From dromasca@avaya.com Fri May 1 12:18:28 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E19043A691D; Fri, 1 May 2009 12:18:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.515 X-Spam-Level: X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soUy03ovqHyI; Fri, 1 May 2009 12:18:27 -0700 (PDT) Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id D7A5C3A6B82; Fri, 1 May 2009 12:18:26 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,280,1238990400"; d="scan'208";a="160109256" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 01 May 2009 15:19:44 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 01 May 2009 15:19:44 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 1 May 2009 21:19:35 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for May 7, 2009 Telechat Thread-Index: AcnJ6fXwkkHGvmBrTk6rLche5FkltwApzUvA From: "Romascanu, Dan (Dan)" To: , , , Subject: [dns-dir] FW: PRELIMINARY Agenda and Package for May 7, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 19:18:29 -0000 Please find below the preliminary agenda of the May 7 telechat. Please review the relevant documents and WG charters brought up for the IESG approval and send me your questions, comments, and concerns before 5/6 COB the latest.=20 Thanks and Regards, Dan =20 INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the May 7, 2009 IESG Teleconference This agenda was generated at 15:34:18 EDT, April 30, 2009 Web version of this agenda can be found at: http://www.ietf.org/IESG/agenda.html =20 =20 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item o draft-ietf-tcpm-tcpsecure-11.txt Improving TCP's Robustness to Blind In-Window Attacks (Proposed Standard) -=20 1 of 11=20 Note: IESG: Please read the Document Shepherd Writeup, we need to discuss=20 the "Updates: 793" issue.=20 Token: Lars Eggert o draft-ietf-tsvwg-rsvp-proxy-proto-08.txt RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard)=20 - 2 of 11=20 Note: Please read the informational document=20 draft-ietf-tsvwg-rsvp-proxy-approaches before this one!=20 Token: Magnus Westerlund o draft-ietf-mpls-p2mp-te-mib-09.txt Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic=20 Engineering (TE) Management Information Base (MIB) module (Proposed=20 Standard) - 3 of 11=20 Token: Ross Callon o draft-ietf-radext-design-07.txt RADIUS Design Guidelines (BCP) - 4 of 11=20 Token: Dan Romascanu o draft-ietf-mipshop-mos-dhcp-options-13.txt Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE=20 802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 of 11 =20 Token: Jari Arkko o draft-ietf-isms-tmsm-17.txt Transport Subsystem for the Simple Network Management Protocol (SNMP) (Proposed Standard) - 6 of 11=20 Token: Pasi Eronen o draft-ietf-isms-transport-security-model-13.txt Transport Security Model for SNMP (Proposed Standard) - 7 of 11=20 Token: Pasi Eronen o draft-ietf-isms-secshell-16.txt Secure Shell Transport Model for SNMP (Proposed Standard) - 8 of 11=20 Token: Pasi Eronen o draft-ietf-isms-radius-usage-06.txt Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models (Proposed Standard) - 9=20 of 11=20 Token: Pasi Eronen o draft-ietf-dccp-serv-codes-09.txt The DCCP Service Code (Proposed Standard) - 10 of 11=20 Token: Lars Eggert o draft-ietf-mipshop-rfc5268bis-01.txt Mobile IPv6 Fast Handovers (Proposed Standard) - 11 of 11=20 Token: Jari Arkko 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-thomson-beep-async-02.txt Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP)=20 (Proposed Standard) - 1 of 2=20 Note: Chris Newman is the document shepherd..=20 Token: Alexey Melnikov o draft-ncook-urlauth-accessid-02.txt Internet Message Access Protocol (IMAP) - URL Access Identifier Extension=20 (Proposed Standard) - 2 of 2=20 Note: Eric Burger is the document shepherd. This document is a Normative=20 dependency for a Lemonade WG document, updating another Lemonade document..=20 Token: Alexey Melnikov 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item o draft-ietf-tcpm-ecnsyn-08.txt Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK=20 Packets (Experimental) - 1 of 5=20 Token: Lars Eggert o draft-ietf-lemonade-notifications-10.txt Lemonade Notifications Architecture (Informational) - 2 of 5=20 Note: Eric Burger is the document shepherd.=20 Token: Alexey Melnikov o draft-ietf-openpgp-camellia-04.txt The Camellia Cipher in OpenPGP (Informational) - 3 of 5=20 Note: Derek Atkins has agreed to shepherd=20 Token: Tim Polk o draft-ietf-roll-indus-routing-reqs-05.txt Industrial Routing Requirements in Low Power and Lossy Networks=20 (Informational) - 4 of 5=20 Note: This I-D was updated after IETF last call to synchronise with IESG=20 review comments made for draft-ietf-roll-urban-routing-reqs. It also pickes=20 up GenArt review coments.=20 Token: Adrian Farrel o draft-ietf-tsvwg-rsvp-proxy-approaches-06.txt RSVP Proxy Approaches (Informational) - 5 of 5=20 Note: Read this before the Protocol document=20 Token: Magnus Westerlund 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item o draft-p2pi-cooper-workshop-report-01.txt Report from the IETF workshop on P2P Infrastructure, May 28, 2008=20 (Informational) - 1 of 1=20 Token: Cullen Jennings 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item o draft-brusilovsky-pak-10.txt Password-Authenticated Diffie-Hellman Exchange (PAK) (Informational) - 1 of=20 2=20 Token: Tim Polk o draft-templin-isatapv4-02.txt Transmission of IPv4 Packets over ISATAP Interfaces (Informational) - 2 of=20 2=20 Token: Jari Arkko 3.3.2 Returning Item o draft-saleem-msml-08.txt Media Server Markup Language (MSML) (Informational) - 1 of 1=20 Token: Robert Sparks 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Yet Another Mail (yam) - 1 of 3 Token: Alexey Melnikov o STORage Maintenance (storm) - 2 of 3 Token: Lars Eggert o Extensible Messaging and Presence Protocol (xmpp) - 3 of 3 Token: Cullen Jennings 4.1.2 Proposed for Approval o Open Authentication Protocol (oauth) - 1 of 1 Token: Lisa Dusseault 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE From ogud@ogud.com Fri May 1 12:54:23 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09DF83A6D74 for ; Fri, 1 May 2009 12:54:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.326 X-Spam-Level: X-Spam-Status: No, score=-2.326 tagged_above=-999 required=5 tests=[AWL=0.273, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oglW4oqY2xoX for ; Fri, 1 May 2009 12:54:21 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 58A353A6CBB for ; Fri, 1 May 2009 12:54:20 -0700 (PDT) Received: from Puki.ogud.com (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n41JtcjJ008552; Fri, 1 May 2009 15:55:38 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200905011955.n41JtcjJ008552@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 01 May 2009 15:55:29 -0400 To: "Romascanu, Dan (Dan)" , From: Olafur Gudmundsson In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: Re: [dns-dir] FW: PRELIMINARY Agenda and Package for May 7, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 19:54:23 -0000 No DNS Early Warning document on the agenda. Olafur At 15:19 01/05/2009, Romascanu, Dan (Dan) wrote: >Please find below the preliminary agenda of the May 7 telechat. Please >review the relevant documents and WG charters brought up for the IESG >approval and send me your questions, comments, and concerns before 5/6 >COB the latest. > >Thanks and Regards, > >Dan > > > >INTERNET ENGINEERING STEERING GROUP (IESG) >Summarized Agenda for the May 7, 2009 IESG Teleconference > >This agenda was generated at 15:34:18 EDT, April 30, 2009 >Web version of this agenda can be found at: >http://www.ietf.org/IESG/agenda.html > > > > > >2. Protocol Actions > Reviews should focus on these questions: "Is this document a > reasonable basis on which to build the salient part of the >Internet > infrastructure? If not, what changes would make it so?" > > >2.1 WG Submissions >2.1.1 New Item > o draft-ietf-tcpm-tcpsecure-11.txt > Improving TCP's Robustness to Blind In-Window Attacks (Proposed >Standard) - > 1 of 11 > Note: IESG: Please read the Document Shepherd Writeup, we need to >discuss > the "Updates: 793" issue. > Token: Lars Eggert > o draft-ietf-tsvwg-rsvp-proxy-proto-08.txt > RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed >Standard) > - 2 of 11 > Note: Please read the informational document > draft-ietf-tsvwg-rsvp-proxy-approaches before this one! > Token: Magnus Westerlund > o draft-ietf-mpls-p2mp-te-mib-09.txt > Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic > Engineering (TE) Management Information Base (MIB) module (Proposed > Standard) - 3 of 11 > Token: Ross Callon > o draft-ietf-radext-design-07.txt > RADIUS Design Guidelines (BCP) - 4 of 11 > Token: Dan Romascanu > o draft-ietf-mipshop-mos-dhcp-options-13.txt > Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for >IEEE > 802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 of >11 > > Token: Jari Arkko > o draft-ietf-isms-tmsm-17.txt > Transport Subsystem for the Simple Network Management Protocol >(SNMP) > > (Proposed Standard) - 6 of 11 > Token: Pasi Eronen > o draft-ietf-isms-transport-security-model-13.txt > Transport Security Model for SNMP (Proposed Standard) - 7 of 11 > Token: Pasi Eronen > o draft-ietf-isms-secshell-16.txt > Secure Shell Transport Model for SNMP (Proposed Standard) - 8 of 11 > Token: Pasi Eronen > o draft-ietf-isms-radius-usage-06.txt > Remote Authentication Dial-In User Service (RADIUS) Usage for Simple > > Network Management Protocol (SNMP) Transport Models (Proposed >Standard) - 9 > of 11 > Token: Pasi Eronen > o draft-ietf-dccp-serv-codes-09.txt > The DCCP Service Code (Proposed Standard) - 10 of 11 > Token: Lars Eggert > o draft-ietf-mipshop-rfc5268bis-01.txt > Mobile IPv6 Fast Handovers (Proposed Standard) - 11 of 11 > Token: Jari Arkko > >2.1.2 Returning Item >NONE > >2.2 Individual Submissions >2.2.1 New Item > o draft-thomson-beep-async-02.txt > Asynchronous Channels for the Blocks Extensible Exchange Protocol >(BEEP) > (Proposed Standard) - 1 of 2 > Note: Chris Newman is the document shepherd.. > Token: Alexey Melnikov > o draft-ncook-urlauth-accessid-02.txt > Internet Message Access Protocol (IMAP) - URL Access Identifier >Extension > (Proposed Standard) - 2 of 2 > Note: Eric Burger is the document shepherd. This document is a >Normative > dependency for a Lemonade WG document, updating another Lemonade >document.. > Token: Alexey Melnikov > >2.2.2 Returning Item >NONE > >3. Document Actions > >3.1 WG Submissions > Reviews should focus on these questions: "Is this document a >reasonable > contribution to the area of Internet engineering which it >covers? If > not, what changes would make it so?" > >3.1.1 New Item > o draft-ietf-tcpm-ecnsyn-08.txt > Adding Explicit Congestion Notification (ECN) Capability to TCP's >SYN/ACK > Packets (Experimental) - 1 of 5 > Token: Lars Eggert > o draft-ietf-lemonade-notifications-10.txt > Lemonade Notifications Architecture (Informational) - 2 of 5 > Note: Eric Burger is the document shepherd. > Token: Alexey Melnikov > o draft-ietf-openpgp-camellia-04.txt > The Camellia Cipher in OpenPGP (Informational) - 3 of 5 > Note: Derek Atkins has agreed to shepherd > Token: Tim Polk > o draft-ietf-roll-indus-routing-reqs-05.txt > Industrial Routing Requirements in Low Power and Lossy Networks > (Informational) - 4 of 5 > Note: This I-D was updated after IETF last call to synchronise with >IESG > review comments made for draft-ietf-roll-urban-routing-reqs. It also >pickes > up GenArt review coments. > Token: Adrian Farrel > o draft-ietf-tsvwg-rsvp-proxy-approaches-06.txt > RSVP Proxy Approaches (Informational) - 5 of 5 > Note: Read this before the Protocol document > Token: Magnus Westerlund > >3.1.2 Returning Item >NONE > >3.2 Individual Submissions Via AD > Reviews should focus on these questions: "Is this document a >reasonable > contribution to the area of Internet engineering which it >covers? If > not, what changes would make it so?" > >3.2.1 New Item > o draft-p2pi-cooper-workshop-report-01.txt > Report from the IETF workshop on P2P Infrastructure, May 28, 2008 > (Informational) - 1 of 1 > Token: Cullen Jennings > >3.2.2 Returning Item >NONE >3.3 Independent Submissions Via RFC Editor > The IESG will use RFC 3932 responses: 1) The IESG has not > found any conflict between this document and IETF work; 2) The > IESG thinks that this work is related to IETF work done in WG > , but this does not prevent publishing; 3) The IESG thinks > that publication is harmful to work in WG and recommends > not publishing at this time; 4) The IESG thinks that this > document violates the IETF procedures for and should > therefore not be published without IETF review and IESG > approval; 5) The IESG thinks that this document extends an > IETF protocol in a way that requires IETF review and should > therefore not be published without IETF review and IESG >approval. > > The document shepherd must propose one of these responses in > the Data Tracker note and supply complete text in the IESG > Note portion of the write-up. The Area Director ballot positions > indicate consensus with the response proposed by the > document shepherd. > > Other matters may be recorded in comments, and the comments will > be passed on to the RFC Editor as community review of the >document. > > >3.3.1 New Item > o draft-brusilovsky-pak-10.txt > Password-Authenticated Diffie-Hellman Exchange (PAK) (Informational) >- >1 of > 2 > Token: Tim Polk > o draft-templin-isatapv4-02.txt > Transmission of IPv4 Packets over ISATAP Interfaces (Informational) >- >2 of > 2 > Token: Jari Arkko > >3.3.2 Returning Item > o draft-saleem-msml-08.txt > Media Server Markup Language (MSML) (Informational) - 1 of 1 > Token: Robert Sparks > > >4. Working Group Actions >4.1 WG Creation >4.1.1 Proposed for IETF Review > o Yet Another Mail (yam) - 1 of 3 > Token: Alexey Melnikov > o STORage Maintenance (storm) - 2 of 3 > Token: Lars Eggert > o Extensible Messaging and Presence Protocol (xmpp) - 3 of 3 > Token: Cullen Jennings >4.1.2 Proposed for Approval > o Open Authentication Protocol (oauth) - 1 of 1 > Token: Lisa Dusseault >4.2 WG Rechartering >4.2.1 Under evaluation for IETF Review > NONE >4.2.2 Proposed for Approval > NONE > > > > >_______________________________________________ >dns-dir mailing list >dns-dir@ietf.org >https://www.ietf.org/mailman/listinfo/dns-dir From peter@denic.de Fri May 1 12:56:09 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30CFE3A6CB2 for ; Fri, 1 May 2009 12:56:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.989 X-Spam-Level: X-Spam-Status: No, score=-5.989 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2N50Ot+BDoX0 for ; Fri, 1 May 2009 12:56:08 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 5AE063A6D5E for ; Fri, 1 May 2009 12:55:51 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1LzyrB-0002Dr-9b; Fri, 01 May 2009 21:57:13 +0200 Received: from localhost by x27.adm.denic.de with local id 1Lzynr-0003rS-Ag; Fri, 01 May 2009 21:53:47 +0200 Date: Fri, 1 May 2009 21:53:47 +0200 From: Peter Koch To: "Romascanu, Dan (Dan)" Message-ID: <20090501195347.GA12952@x27.adm.denic.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: dns-dir@ietf.org Subject: Re: [dns-dir] FW: PRELIMINARY Agenda and Package for May 7, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 19:56:09 -0000 On Fri, May 01, 2009 at 09:19:35PM +0200, Romascanu, Dan (Dan) wrote: > o draft-ietf-mipshop-mos-dhcp-options-13.txt > Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for > IEEE > 802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 of > 11 discussion is ongoing between Patrik, myself and the authors. > o draft-ietf-isms-secshell-16.txt > Secure Shell Transport Model for SNMP (Proposed Standard) - 8 of 11 > Token: Pasi Eronen Could someone please double check the reference to RFC 3490 (IDN) in there? > o draft-ietf-dccp-serv-codes-09.txt > The DCCP Service Code (Proposed Standard) - 10 of 11 > Token: Lars Eggert This mentions the DNS SRV RR type as a generally available method without going into detail; doesn't seem to have buried issues. > o draft-p2pi-cooper-workshop-report-01.txt > Report from the IETF workshop on P2P Infrastructure, May 28, 2008 > (Informational) - 1 of 1 NIT: The draft claims to aim at "Standards Track" > o draft-templin-isatapv4-02.txt > Transmission of IPv4 Packets over ISATAP Interfaces (Informational) NIT: RFC 1035 appears in the bibliography without reference -Peter From rdroms@cisco.com Fri May 1 13:00:23 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E77643A6D5E for ; Fri, 1 May 2009 13:00:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.583 X-Spam-Level: X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PabUbRn-wGae for ; Fri, 1 May 2009 13:00:23 -0700 (PDT) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id DFF453A6C51 for ; Fri, 1 May 2009 13:00:22 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,280,1238976000"; d="scan'208";a="43210713" Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 01 May 2009 20:01:46 +0000 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n41K1kI0004224; Fri, 1 May 2009 16:01:46 -0400 Received: from bxb-rdroms-8713.cisco.com (bxb-rdroms-8713.cisco.com [10.98.10.84]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n41K1jI6009422; Fri, 1 May 2009 20:01:45 GMT Message-Id: From: Ralph Droms To: Peter Koch In-Reply-To: <20090501195347.GA12952@x27.adm.denic.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 1 May 2009 16:01:45 -0400 References: <20090501195347.GA12952@x27.adm.denic.de> X-Mailer: Apple Mail (2.930.3) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1610; t=1241208106; x=1242072106; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20 |Subject:=20Re=3A=20[dns-dir]=20FW=3A=20PRELIMINARY=20Agend a=20and=20Package=20for=20May=207,=202009=20Telechat |Sender:=20 |To:=20Peter=20Koch=20; bh=NONzmeOXCMVN9avKYkbqJK/gd+whZaVzX8JLHpUWdQE=; b=Dm/3h0tl3vfaH3inZ9tFW/xszKSVxpU0OiC4yVDg3IhS7FZiFF0T5fc2kO l+zN9iSixYjHtRyZeVbGiUKpXguE44PYqaGpt/3i4QwJUS7V0oQIw7gjn1cv uC5x1lSr1S; Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); Cc: dns-dir@ietf.org Subject: Re: [dns-dir] FW: PRELIMINARY Agenda and Package for May 7, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 20:00:24 -0000 Peter - what is the nature of your discussion regarding draft-ietf- mipshop-mos-dhcp-options-13.txt? - Ralph On May 1, 2009, at 3:53 PM 5/1/09, Peter Koch wrote: > On Fri, May 01, 2009 at 09:19:35PM +0200, Romascanu, Dan (Dan) wrote: > >> o draft-ietf-mipshop-mos-dhcp-options-13.txt >> Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options >> for >> IEEE >> 802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 >> of >> 11 > > discussion is ongoing between Patrik, myself and the authors. > >> o draft-ietf-isms-secshell-16.txt >> Secure Shell Transport Model for SNMP (Proposed Standard) - 8 of >> 11 >> Token: Pasi Eronen > > Could someone please double check the reference to RFC 3490 (IDN) in > there? > >> o draft-ietf-dccp-serv-codes-09.txt >> The DCCP Service Code (Proposed Standard) - 10 of 11 >> Token: Lars Eggert > > This mentions the DNS SRV RR type as a generally available method > without > going into detail; doesn't seem to have buried issues. > >> o draft-p2pi-cooper-workshop-report-01.txt >> Report from the IETF workshop on P2P Infrastructure, May 28, 2008 >> (Informational) - 1 of 1 > > NIT: The draft claims to aim at "Standards Track" > >> o draft-templin-isatapv4-02.txt >> Transmission of IPv4 Packets over ISATAP Interfaces >> (Informational) > > NIT: RFC 1035 appears in the bibliography without reference > > -Peter > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir From peter@denic.de Fri May 1 13:31:09 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0EBA3A6D95 for ; Fri, 1 May 2009 13:31:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.998 X-Spam-Level: X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmoHdBd6jn5y for ; Fri, 1 May 2009 13:31:07 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id C2DED3A6CFC for ; Fri, 1 May 2009 13:30:46 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1LzzOx-0002j6-2a; Fri, 01 May 2009 22:32:07 +0200 Received: from localhost by x27.adm.denic.de with local id 1LzzLd-00043p-3L; Fri, 01 May 2009 22:28:41 +0200 Date: Fri, 1 May 2009 22:28:41 +0200 From: Peter Koch To: Ralph Droms Message-ID: <20090501202841.GB12952@x27.adm.denic.de> References: <20090501195347.GA12952@x27.adm.denic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: gabor.bajko@nokia.com, dns-dir@ietf.org Subject: Re: [dns-dir] FW: PRELIMINARY Agenda and Package for May 7, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 20:31:09 -0000 On Fri, May 01, 2009 at 04:01:45PM -0400, Ralph Droms wrote: > Peter - what is the nature of your discussion regarding draft-ietf- > mipshop-mos-dhcp-options-13.txt? I'm sorry, I confused this with . It seems that draft-ietf-mipshop-mos-dhcp-options-13.txt contains an answer to an important question raised for "dns-discovery-04": _which_ domain names serve as entry points into the (S-)NAPTR schema? Instead of overloading the DNS FQDN or the DNS search path, this draft actually provides a simple - and straightforward - solution: a per protocol/application list of domain names as starting points for subsequent S-NAPTR lookups (well, that's NAPTR lookups as per RFC 3958). Not sure why so many levels of indirection are desired, but this interaction looks ok. This text in section 3 is a bit confusing The Sub-option MAY contain multiple domain names, but these should Refer to the NAPTR records of different providers, rather than different A records within the same provider. That is, the use of multiple domain names is not meant to replace NAPTR and SRV records, but rather to allow a single DHCP server to indicate MIH servers operated by multiple providers. NIT: s/Refer/refer/ I'd say that the multiple domain names are intended to serve as starting point for the resolution mechanism described in [MoS-DNS] rather than directly being resolved into address (A/AAAA) records. And this probably ought to be at a MUST level. Now, when this draft gives the mandatory source for [MoS-DNS] - fine. Operationally it would help if the domain names used as [MoS-DNS] 'hooks' would not only be at the registration level, but that's a distraction for now. (The reason is to avoid lots of NAPTR RRSets at the top 'domain' name or zone apex). -Peter From ogud@ogud.com Tue May 5 11:28:39 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E97F53A6B55 for ; Tue, 5 May 2009 11:28:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJVojUMRsnvV for ; Tue, 5 May 2009 11:28:39 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id BF4B03A6CAD for ; Tue, 5 May 2009 11:28:38 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n45IU1IT015205 for ; Tue, 5 May 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 5 May 2009 14:30:01 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090505_183001_025206.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ietf-mipshop-mos-dhcp-options-14.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 18:28:40 -0000 Count: 11 Internet Engineering Task force Gabor Bajko Internet Draft Nokia Intended Status: Proposed Standard Subir Das Expires: October 31, 2009 Telcordia Technologies May 01, 2009 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery draft-ietf-mipshop-mos-dhcp-options-14 Abstract This document defines new Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) options that contain a list of IP addresses and a list of domain names that can be mapped to servers providing IEEE 802.21 type of Mobility Service (MoS)[MSFD]. These Mobility Services are used to assist a mobile node (MN) in handover preparation (network discovery) and handover decision (network selection). The services addressed in this document are the Media Independent Handover Services defined in [IEEE802.21]. From ogud@ogud.com Tue May 5 11:49:49 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E52A33A6969 for ; Tue, 5 May 2009 11:49:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.335 X-Spam-Level: X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6c+hCd+yH9YZ for ; Tue, 5 May 2009 11:49:49 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id EF2F73A691B for ; Tue, 5 May 2009 11:49:48 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n45IU0ER015196 for ; Tue, 5 May 2009 14:30:00 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 5 May 2009 14:30:00 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090505_183000_051620.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ietf-sipcore-sec-flows-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 18:49:50 -0000 Count: 11 Network Working Group C. Jennings Internet-Draft Cisco Systems Intended status: Standards Track K. Ono Expires: November 5, 2009 NTT Corporation R. Sparks B. Hibbard, Ed. Tekelec May 4, 2009 Example call flows using Session Initiation Protocol (SIP) security mechanisms draft-ietf-sipcore-sec-flows-00 Abstract This document shows example call flows demonstrating the use of Transport Layer Security (TLS), and Secure/Multipurpose Internet Mail Extensions (S/MIME) in Session Initiation Protocol (SIP). It also provides information that helps implementers build interoperable SIP software. To help facilitate interoperability testing, it includes certificates used in the example call flows and processes to create certificates for testing. From ogud@ogud.com Tue May 12 07:37:48 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BC6F3A6EF3 for ; Tue, 12 May 2009 07:37:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.921 X-Spam-Level: X-Spam-Status: No, score=-0.921 tagged_above=-999 required=5 tests=[AWL=-1.036, BAYES_40=-0.185, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+FHCD15qL2p for ; Tue, 12 May 2009 07:37:47 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id CF7FB3A6EFA for ; Tue, 12 May 2009 07:37:42 -0700 (PDT) Received: from Puki.ogud.com (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4CEdDd7004231 for ; Tue, 12 May 2009 10:39:13 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200905121439.n4CEdDd7004231@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 12 May 2009 10:38:42 -0400 To: dns-dir@ietf.org From: =?iso-8859-1?Q?=D3lafur?= =?iso-8859-1?Q?_Gu=F0mundsson?= /DNSEXT chair Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] Is the mail archive private yet ? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 14:37:48 -0000 Ignore, just checking. Olafur From ogud@ogud.com Tue May 12 07:40:07 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 395EB28C104 for ; Tue, 12 May 2009 07:40:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.369 X-Spam-Level: X-Spam-Status: No, score=-1.369 tagged_above=-999 required=5 tests=[AWL=-0.559, BAYES_05=-1.11, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UsHlKPTSrNaB for ; Tue, 12 May 2009 07:40:06 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 431E73A6D7F for ; Tue, 12 May 2009 07:40:06 -0700 (PDT) Received: from Puki.ogud.com (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4CEfaac004292; Tue, 12 May 2009 10:41:36 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200905121441.n4CEfaac004292@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 12 May 2009 10:41:07 -0400 To: =?iso-8859-1?Q?=D3lafur?= =?iso-8859-1?Q?_Gu=F0mundsson?= /DNSEXT chair , dns-dir@ietf.org From: Olafur Gudmundsson In-Reply-To: <200905121439.n4CEdDd7004231@stora.ogud.com> References: <200905121439.n4CEdDd7004231@stora.ogud.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: Re: [dns-dir] Is the mail archive private yet ? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 14:40:07 -0000 Answer is no, we need a new list. At 10:39 12/05/2009, =D3lafur Gu=F0mundsson /DNSEXT wrote: >Ignore, just checking. > > Olafur From ogud@ogud.com Tue May 12 11:28:30 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE6EE3A684B for ; Tue, 12 May 2009 11:28:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.254 X-Spam-Level: X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.345, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ue46mkDE-jAy for ; Tue, 12 May 2009 11:28:30 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id D3AC03A6CBF for ; Tue, 12 May 2009 11:28:29 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4CIU0Eu007432 for ; Tue, 12 May 2009 14:30:00 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 12 May 2009 14:30:00 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090512_183000_008580.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ietf-ipsecme-ikev2-redirect-09.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 18:28:30 -0000 Count: 13 Network Working Group V. Devarapalli Internet-Draft WiChorus Intended status: Standards Track K. Weniger Expires: November 12, 2009 May 11, 2009 Redirect Mechanism for IKEv2 draft-ietf-ipsecme-ikev2-redirect-09.txt Abstract IKEv2 is a protocol for setting up VPN tunnels from a remote location to a gateway so that the VPN client can access services in the network behind the gateway. Currently there is no standard mechanism specified that allows an overloaded VPN gateway or a VPN gateway that is being shut down for maintenance to redirect the VPN client to attach to another gateway. This document proposes a redirect mechanism for IKEv2. The proposed mechanism can also be used in Mobile IPv6 to enable the home agent to redirect the mobile node to another home agent. From dromasca@avaya.com Wed May 13 09:03:59 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7279B3A68CC; Wed, 13 May 2009 09:03:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.505 X-Spam-Level: X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zn7jAw6DwQnE; Wed, 13 May 2009 09:03:58 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id B54583A6A7A; Wed, 13 May 2009 09:03:57 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,188,1241409600"; d="scan'208";a="145693965" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 13 May 2009 12:05:27 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 13 May 2009 12:05:26 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 13 May 2009 18:05:08 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Review: Extensible Messaging and Presence Protocol (xmpp) Thread-Index: AcnTSfQmei1IW6mzTNKP+kHyt1ENVwAmmwaw From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: WG Review: Extensible Messaging and Presence Protocol (xmpp) X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 16:03:59 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Wednesday, May 13, 2009 12:37 AM To: IETF Announcement list Subject: WG Review: Extensible Messaging and Presence Protocol (xmpp)=20 A new IETF working group has been proposed in the Real-time Applications and Infrastructure Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, May 19, 2009. Extensible Messaging and Presence Protocol (xmpp) ------------------------------------------------- Last Modified: 2009-04-27 Current Status: Proposed Working Group Chair(s): TBD Area Director(s): Robert Sparks Cullen Jennings Area Advisor: TBD Mailing Lists: General Discussion: xmpp@ietf.org Description of Working Group: The Extensible Messaging and Presence Protocol (XMPP) is an technology for the near-real-time exchange of messages and presence notifications, where data is exchanged over Extensible Markup Language (XML) streams. XMPP was originally formalized by the XMPP Working Group in 2002-2004, resulting in publication of RFCs 3920-3923. Implementation and deployment experience since that time has resulted in errata, clarifications, and suggestions for improvement to the core XMPP specifications (RFCs 3920 and 3921). Some technologies on which XMPP depends (e.g., Transport Layer Security and the Simple Authentication and Security Layer) have undergone modifications of their own, which XMPP needs to track. Finally, the group needs to define a sustainable solution to internationalization of XMPP addresses, since the approach taken in RFC 3920 (based on stringprep profiles) is limited to Unicode 3.2 characters. Both draft-saintandre-rfc3920bis-* and draft-saintandre-rfc3921bis-* reflect community input so far regarding these modifications, but the group needs to complete this work, especially with regard to internationalization. Because of the scope of changes involved, it is envisioned that these specifications will be cycled at Proposed Standard. Although RFC 3923 defines an end-to-end signing and encryption technology for use by XMPP systems, to date it has not been implemented. A goal of the group is to develop an implementable method for end-to-end encryption, preferably based on well known and widely deployed security technologies. XMPP uses TLS for encryption and the Simple Authentication and Security Layer (SASL) for authentication. In the case of a server-to-server stream, XMPP is deployed using TLS and the SASL EXTERNAL mechanism, where each peer presents an X.509 certificate. This model introduces scaling challenges in multi-domain deployments because RFC 3920 requires that a stream cannot be reused for more than one domain, thus necessitating multiple TCP connections. The group will work to overcome these challenges by defining an optional mechanism for using a single connection with multiple identities. It is anticipated that most of the work will consist of defining and providing requirements to the TLS and SASL working groups. Many of the core and extended features of XMPP have also been implemented in technologies based on the Session Initiation Protocol (SIP). To ensure interworking between XMPP systems and SIP systems, a number of Internet-Drafts (draft-saintandre-sip-xmpp-*) have been produced. The group will define a framework within which this work could be completed. In completing its work, the group will strive to retain backwards compatibility with RFCs 3920 and 3921. However, changes that are not backwards compatible might be accepted if the group determines that the changes are required to meet the group's technical objectives and the group clearly documents the reasons for making them. Goals and Milestones: - Deliver rfc3920bis and rfc3921bis to the IESG. - Decide upon a direction for end-to-end encryption. - Decide upon a direction for server-to-server connection reuse. - Define a framework for SIP-XMPP interworking. - Define a solution for end-to-end encryption. - Define a solution for server-to-server connection reuse. From ogud@ogud.com Wed May 13 11:28:34 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0CF828C202 for ; Wed, 13 May 2009 11:28:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.252 X-Spam-Level: X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qwouf-ZRRXjg for ; Wed, 13 May 2009 11:28:34 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id D815728C115 for ; Wed, 13 May 2009 11:28:33 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4DIU1iL005700 for ; Wed, 13 May 2009 14:30:02 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Wed, 13 May 2009 14:30:02 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090513_183002_018488.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ietf-manet-olsrv2-mib-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 18:28:34 -0000 Count: 475 Internet Engineering Task Force R. Cole Internet-Draft Johns Hopkins University Intended status: Standards Track T. Clausen Expires: November 4, 2009 LIX, Ecole Polytechnique May 3, 2009 Definition of Managed Objects for the MANET Optimized Link State Routing Protocol version 2 draft-ietf-manet-olsrv2-mib-00 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring and managing aspects of the Optimized Link State Routing protocol version 2. The Optimized Link State Routing MIB also reports state information, performance metrics, and notifications. In addition to configuration, this additional state and performance information is useful to management stations troubleshooting Mobile Ad-Hoc Networks routing problems. From ogud@ogud.com Thu May 14 11:28:33 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B940828C275 for ; Thu, 14 May 2009 11:28:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.257 X-Spam-Level: X-Spam-Status: No, score=-2.257 tagged_above=-999 required=5 tests=[AWL=0.342, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUKFMudaK1Ls for ; Thu, 14 May 2009 11:28:33 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 6686328C20D for ; Thu, 14 May 2009 11:28:32 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4EIU1pW046487 for ; Thu, 14 May 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Thu, 14 May 2009 14:30:01 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090514_183001_034039.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ietf-pkix-prqp-03.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 18:28:33 -0000 Count: 25 PKIX Working Group M. Pala Internet-Draft Dartmouth College Intended status: Experimental May 13, 2009 Expires: November 14, 2009 PKI Resource Query Protocol (PRQP) draft-ietf-pkix-prqp-03 Abstract One of the most strategic problems still open in PKIX is locating public data and services associated with a Certification Authority (CA). This issue impacts interoperability and usability in PKIX. This draft describes the PKI Resource Query Protocol (PRQP), its design, definition, and its impact in already deployed PKIX protocols. From dromasca@avaya.com Thu May 14 23:26:44 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 688443A68C9; Thu, 14 May 2009 23:26:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.504 X-Spam-Level: X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m03iAVbHQaLI; Thu, 14 May 2009 23:26:43 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 608A43A6DA6; Thu, 14 May 2009 23:26:04 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,198,1241409600"; d="scan'208";a="145883220" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 15 May 2009 02:27:35 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 15 May 2009 02:27:35 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 15 May 2009 08:27:13 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for May 21, 2009 Telechat Thread-Index: AcnU64HUh0J0jKlISmOP7CpjIvwR8AAOjaRQ From: "Romascanu, Dan (Dan)" To: , , , Subject: [dns-dir] FW: PRELIMINARY Agenda and Package for May 21, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 06:26:44 -0000 =20 Please find below the preliminary agenda of the 5/21 IESG telechat. Please send me your comments, questions, and concerns before 5/20 COB. Thanks and Regards, Dan =20 2.1 WG Submissions 2.1.1 New Item o draft-ietf-tsvwg-rsvp-proxy-proto-09.txt RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard)=20 - 1 of 3=20 Note: Please read the informational document=20 draft-ietf-tsvwg-rsvp-proxy-approaches before this one!=20 Token: Magnus Westerlund o draft-ietf-netlmm-pmip6-ipv4-support-12.txt IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 2 of 3=20 Token: Jari Arkko o draft-ietf-dccp-simul-open-08.txt DCCP Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal =20 (Proposed Standard) - 3 of 3=20 Token: Lars Eggert 2.1.2 Returning Item o draft-ietf-pkix-3281update-05.txt An Internet Attribute Certificate Profile for Authorization (Proposed Standard) - 1 of 1=20 Token: Tim Polk 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item o draft-groves-megaco-pkgereg-03.txt H.248/MEGACO Registration Procedures (BCP) - 1 of 1=20 Note: IESG - when reviewing this, please consider the topic of if it is=20 alright to register a "public" package when the specification is not publicly available. This came up as an IETF LC comment.=20 Token: Cullen Jennings 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item o draft-ietf-tcpm-ecnsyn-09.txt Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK=20 Packets (Experimental) - 1 of 3=20 Token: Lars Eggert o draft-ietf-dkim-overview-11.txt DomainKeys Identified Mail (DKIM) Service Overview (Informational) - 2 of 3=20 Token: Pasi Eronen o draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt RSVP Proxy Approaches (Informational) - 3 of 3=20 Note: Read this before the Protocol document=20 Token: Magnus Westerlund 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item NONE 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item NONE 3.3.3 For Action o draft-templin-seal-23.txt The Subnetwork Encapsulation and Adaptation Layer (SEAL) (Informational) -=20 1 of 2=20 Note: Brought back to the agenda because of desired status change (now Inf)=20 Token: Jari Arkko o draft-ford-behave-top-06.txt Unintended Consequence of two NAT deployments with Overlapping Address =20 Space (Informational) - 2 of 2=20 Token: Russ Housley 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval o Yet Another Mail (yam) - 1 of 2 Token: Alexey Melnikov o Extensible Messaging and Presence Protocol (xmpp) - 2 of 2 Token: Cullen Jennings 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE From ogud@ogud.com Fri May 15 05:29:13 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15D443A6E1D for ; Fri, 15 May 2009 05:29:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.261 X-Spam-Level: X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbXKI0NEcOHQ for ; Fri, 15 May 2009 05:29:12 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id ABACF3A6C42 for ; Fri, 15 May 2009 05:29:11 -0700 (PDT) Received: from Puki.ogud.com (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4FCUaER010575; Fri, 15 May 2009 08:30:36 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200905151230.n4FCUaER010575@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 15 May 2009 08:29:57 -0400 To: "Romascanu, Dan (Dan)" , dns-dir@ietf.org From: Olafur Gudmundsson In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: Re: [dns-dir] FW: PRELIMINARY Agenda and Package for May 21, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 12:29:13 -0000 None in the dns-early-warning archive. Olafur At 02:27 15/05/2009, Romascanu, Dan (Dan) wrote: > > >Please find below the preliminary agenda of the 5/21 IESG telechat. >Please send me your comments, questions, and concerns before 5/20 COB. > >Thanks and Regards, > >Dan > > >2.1 WG Submissions >2.1.1 New Item > o draft-ietf-tsvwg-rsvp-proxy-proto-09.txt > RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed >Standard) > - 1 of 3 > Note: Please read the informational document > draft-ietf-tsvwg-rsvp-proxy-approaches before this one! > Token: Magnus Westerlund > o draft-ietf-netlmm-pmip6-ipv4-support-12.txt > IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 2 of 3 > Token: Jari Arkko > o draft-ietf-dccp-simul-open-08.txt > DCCP Simultaneous-Open Technique to Facilitate NAT/Middlebox >Traversal > > (Proposed Standard) - 3 of 3 > Token: Lars Eggert > >2.1.2 Returning Item > o draft-ietf-pkix-3281update-05.txt > An Internet Attribute Certificate Profile for Authorization >(Proposed > > Standard) - 1 of 1 > Token: Tim Polk > > >2.2 Individual Submissions >2.2.1 New Item >NONE >2.2.2 Returning Item > o draft-groves-megaco-pkgereg-03.txt > H.248/MEGACO Registration Procedures (BCP) - 1 of 1 > Note: IESG - when reviewing this, please consider the topic of if it >is > alright to register a "public" package when the specification is not > > publicly available. This came up as an IETF LC comment. > Token: Cullen Jennings > > >3. Document Actions > >3.1 WG Submissions > Reviews should focus on these questions: "Is this document a >reasonable > contribution to the area of Internet engineering which it >covers? If > not, what changes would make it so?" > >3.1.1 New Item > o draft-ietf-tcpm-ecnsyn-09.txt > Adding Explicit Congestion Notification (ECN) Capability to TCP's >SYN/ACK > Packets (Experimental) - 1 of 3 > Token: Lars Eggert > o draft-ietf-dkim-overview-11.txt > DomainKeys Identified Mail (DKIM) Service Overview (Informational) - >2 >of 3 > Token: Pasi Eronen > o draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt > RSVP Proxy Approaches (Informational) - 3 of 3 > Note: Read this before the Protocol document > Token: Magnus Westerlund > >3.1.2 Returning Item >NONE > >3.2 Individual Submissions Via AD > Reviews should focus on these questions: "Is this document a >reasonable > contribution to the area of Internet engineering which it >covers? If > not, what changes would make it so?" > >3.2.1 New Item >NONE >3.2.2 Returning Item >NONE >3.3 Independent Submissions Via RFC Editor > The IESG will use RFC 3932 responses: 1) The IESG has not > found any conflict between this document and IETF work; 2) The > IESG thinks that this work is related to IETF work done in WG > , but this does not prevent publishing; 3) The IESG thinks > that publication is harmful to work in WG and recommends > not publishing at this time; 4) The IESG thinks that this > document violates the IETF procedures for and should > therefore not be published without IETF review and IESG > approval; 5) The IESG thinks that this document extends an > IETF protocol in a way that requires IETF review and should > therefore not be published without IETF review and IESG >approval. > > The document shepherd must propose one of these responses in > the Data Tracker note and supply complete text in the IESG > Note portion of the write-up. The Area Director ballot positions > indicate consensus with the response proposed by the > document shepherd. > > Other matters may be recorded in comments, and the comments will > be passed on to the RFC Editor as community review of the >document. > > >3.3.1 New Item >NONE >3.3.2 Returning Item >NONE >3.3.3 For Action > o draft-templin-seal-23.txt > The Subnetwork Encapsulation and Adaptation Layer (SEAL) >(Informational) - > 1 of 2 > Note: Brought back to the agenda because of desired status change >(now >Inf) > Token: Jari Arkko > o draft-ford-behave-top-06.txt > Unintended Consequence of two NAT deployments with Overlapping >Address > > Space (Informational) - 2 of 2 > Token: Russ Housley > >4. Working Group Actions >4.1 WG Creation >4.1.1 Proposed for IETF Review > NONE >4.1.2 Proposed for Approval > o Yet Another Mail (yam) - 1 of 2 > Token: Alexey Melnikov > o Extensible Messaging and Presence Protocol (xmpp) - 2 of 2 > Token: Cullen Jennings >4.2 WG Rechartering >4.2.1 Under evaluation for IETF Review > NONE >4.2.2 Proposed for Approval > NONE > > >_______________________________________________ >dns-dir mailing list >dns-dir@ietf.org >https://www.ietf.org/mailman/listinfo/dns-dir From ogud@ogud.com Fri May 22 11:28:27 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38B4F3A698F for ; Fri, 22 May 2009 11:28:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.168 X-Spam-Level: X-Spam-Status: No, score=-2.168 tagged_above=-999 required=5 tests=[AWL=0.431, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AuyKhgJABJI9 for ; Fri, 22 May 2009 11:28:26 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 5660D3A6B0E for ; Fri, 22 May 2009 11:28:26 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4MIU1I3083673 for ; Fri, 22 May 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Fri, 22 May 2009 14:30:01 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090522_183001_013084.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-daboo-srv-caldav-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 18:28:27 -0000 Count: 25 Network Working Group C. Daboo Internet-Draft Apple Inc. Expires: November 22, 2009 May 21, 2009 Use of SRV records for locating CalDAV calendar services draft-daboo-srv-caldav-00 Abstract This specification describes how SRV records can be used to locate a CalDAV based calendar service. From ogud@ogud.com Fri May 22 11:57:47 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 425303A6BB9 for ; Fri, 22 May 2009 11:57:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.173 X-Spam-Level: X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[AWL=0.426, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4T0XLZCcapP for ; Fri, 22 May 2009 11:57:46 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 5579B3A6962 for ; Fri, 22 May 2009 11:57:46 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4MIU0o8083664 for ; Fri, 22 May 2009 14:30:00 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Fri, 22 May 2009 14:30:00 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090522_183000_014622.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-daboo-srv-email-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 18:57:47 -0000 Count: 30 Network Working Group C. Daboo Internet-Draft Apple Inc. Expires: November 22, 2009 May 21, 2009 Use of SRV records for locating email services draft-daboo-srv-email-00 Abstract This specification describes how SRV records can be used to locate email services. From dromasca@avaya.com Sun May 24 08:29:03 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E57CE28C0FB; Sun, 24 May 2009 08:29:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.501 X-Spam-Level: X-Spam-Status: No, score=-2.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1XwKvP6PTo6; Sun, 24 May 2009 08:28:57 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id EEF163A6882; Sun, 24 May 2009 08:28:56 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,240,1241409600"; d="scan'208";a="171795375" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 24 May 2009 11:30:36 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 24 May 2009 11:30:35 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 24 May 2009 17:30:21 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Last Call: draft-dusseault-impl-reports (Guidance on Interoperation and Implementation Reports) to BCP Thread-Index: AcnaP4lUW8erJ0OxT6KtiwORTsuLhACRL4TA From: "Romascanu, Dan (Dan)" To: , , , Subject: [dns-dir] FW: Last Call: draft-dusseault-impl-reports (Guidance on Interoperation and Implementation Reports) to BCP X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2009 15:29:04 -0000 I believe that this BCP may have specific implications for each on of the directorates and review teams in OPS, so I suggest that at least one reviewer goes through it in each team and sends relevant LC comments.=20 Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: Thursday, May 21, 2009 9:09 PM To: IETF-Announce Subject: Last Call: draft-dusseault-impl-reports (Guidance on Interoperation and Implementation Reports) to BCP=20 The IESG has received a request from an individual submitter to consider the following document: - 'Guidance on Interoperation and Implementation Reports ' as a BCP The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-06-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-dusseault-impl-reports-02.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag= =3D 17620&rfc_flag=3D0 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From dromasca@avaya.com Sun May 24 09:44:04 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 176E43A6E51; Sun, 24 May 2009 09:44:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8k+8Z7ZRWgA; Sun, 24 May 2009 09:44:03 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 249F428C16B; Sun, 24 May 2009 09:44:03 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,240,1241409600"; d="scan'208";a="171797123" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 24 May 2009 12:45:43 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 24 May 2009 12:45:42 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 24 May 2009 18:45:33 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-dnsext-dnsproxy-05.txt to BCP Thread-Index: AcnbnbfZMXL3u3mPQ3md5nc8ugwWqAA8UM3w From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Evaluation: draft-ietf-dnsext-dnsproxy-05.txt to BCP X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2009 16:44:04 -0000 =20 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dnsext-dnsproxy-05.txt Technical Summary This document is aimed at a target audience that is outside the IETF but implement DNS protocol elements, frequently without much understanding of the DNS protocol. This document gives simple guidance to such people to avoid common mistakes, seen in the field, that cause major interoperabilty issues. Working Group Summary The consensus for this document is real strong. Document Quality This is a high quality draft, that is addressing an important aspect for the interoperabilty of the DNS protocol. Number of vendors that purchase/test DNS gateways have stated that compliance with this document is going to be a purchasing requirement. Personnel Document Shepherd is: Olafur Gudmundsson AD: Ralph Droms RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) From ogud@ogud.com Mon May 25 11:28:22 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 211823A692D for ; Mon, 25 May 2009 11:28:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.248 X-Spam-Level: X-Spam-Status: No, score=-1.248 tagged_above=-999 required=5 tests=[AWL=-0.508, BAYES_20=-0.74] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VaVUalG3v9xE for ; Mon, 25 May 2009 11:28:21 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 481013A6827 for ; Mon, 25 May 2009 11:28:20 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4PIU0SX017402 for ; Mon, 25 May 2009 14:30:00 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Mon, 25 May 2009 14:30:00 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090525_183000_001141.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-speakman-looping-issue-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 18:28:22 -0000 Count: 28 Mobile Ad hoc Networking (MANET) L. Speakman Internet-Draft Research Center for Natural Hazard Intended status: Informational and Disaster Recovery, Niigata Expires: November 25, 2009 University K. Mase Graduate School of Science and Technology, Niigata University May 25, 2009 Routing Loop Issue in Mobile Ad Hoc Networks (MANETs) draft-speakman-looping-issue-00 Abstract This document describes the routing loop and packet looping issues in mobile ad hoc network (MANET) running proactive routing protocols using hop count metric. Mechanisms of loop formation are identified and how the problem of loop formation is exacerbated by the use of Link Layer Notification is described. The effect of the looping packets on the network are shown by comparing against the case where the looping packets are detected and discarded, showing the need for routing loops or looping packets to be dealt with in MANETs. From peter@denic.de Mon May 25 11:47:28 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02D453A6D89 for ; Mon, 25 May 2009 11:47:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.943 X-Spam-Level: X-Spam-Status: No, score=-5.943 tagged_above=-999 required=5 tests=[AWL=0.306, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b2e1deH1owNW for ; Mon, 25 May 2009 11:47:27 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 42F453A6C46 for ; Mon, 25 May 2009 11:47:27 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1M8fEQ-0006TN-46; Mon, 25 May 2009 20:49:06 +0200 Received: from localhost by x27.adm.denic.de with local id 1M8fAu-0007ds-MO; Mon, 25 May 2009 20:45:28 +0200 Date: Mon, 25 May 2009 20:45:28 +0200 From: Peter Koch To: Olafur_DNS_EARLY_WARNING Message-ID: <20090525184528.GR13303@x27.adm.denic.de> References: <20090525_183000_001141.ogud@ogud.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090525_183000_001141.ogud@ogud.com> User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: dns-dir@ietf.org Subject: Re: [dns-dir] DNS Early Warn: draft-speakman-looping-issue-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 18:47:28 -0000 Olafur, On Mon, May 25, 2009 at 02:30:00PM -0400, Olafur_DNS_EARLY_WARNING wrote: > Count: 28 could you disclose what thriggered this high count? > Routing Loop Issue in Mobile Ad Hoc Networks (MANETs) > draft-speakman-looping-issue-00 The draft is more DNS clean than many others, i.e. no issues. Was it "ANY"? -Peter From ogud@ogud.com Mon May 25 12:40:15 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 493783A6F4E for ; Mon, 25 May 2009 12:40:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.172 X-Spam-Level: X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[AWL=0.427, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2T-CczGaiXc6 for ; Mon, 25 May 2009 12:40:14 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 641623A6856 for ; Mon, 25 May 2009 12:40:14 -0700 (PDT) Received: from Puki.ogud.com (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4PJfjdC017986; Mon, 25 May 2009 15:41:45 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200905251941.n4PJfjdC017986@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 25 May 2009 15:40:11 -0400 To: Peter Koch From: Olafur Gudmundsson In-Reply-To: <20090525184528.GR13303@x27.adm.denic.de> References: <20090525_183000_001141.ogud@ogud.com> <20090525184528.GR13303@x27.adm.denic.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Cc: dns-dir@ietf.org Subject: Re: [dns-dir] DNS Early Warn: draft-speakman-looping-issue-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 19:40:15 -0000 At 14:45 25/05/2009, Peter Koch wrote: >Olafur, > >On Mon, May 25, 2009 at 02:30:00PM -0400, Olafur_DNS_EARLY_WARNING wrote: > > Count: 28 > >could you disclose what thriggered this high count? > > > Routing Loop Issue in Mobile Ad Hoc Networks (MANETs) > > draft-speakman-looping-issue-00 > >The draft is more DNS clean than many others, i.e. no issues. Was it "ANY"? They used the word OLSRv2 on 28 lines my script does not require space before or after SRV for a match, probably a mistake. Olafur From peter@denic.de Mon May 25 13:35:42 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDAE13A689B for ; Mon, 25 May 2009 13:35:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.951 X-Spam-Level: X-Spam-Status: No, score=-5.951 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pj-bDrBr0O5E for ; Mon, 25 May 2009 13:35:42 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 376B63A68B4 for ; Mon, 25 May 2009 13:35:41 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1M8gvB-0007Tq-9W; Mon, 25 May 2009 22:37:21 +0200 Received: from localhost by x27.adm.denic.de with local id 1M8grf-0008GS-QD; Mon, 25 May 2009 22:33:43 +0200 Date: Mon, 25 May 2009 22:33:43 +0200 From: Peter Koch To: Olafur Gudmundsson Message-ID: <20090525203343.GS13303@x27.adm.denic.de> References: <20090525_183000_001141.ogud@ogud.com> <20090525184528.GR13303@x27.adm.denic.de> <200905251941.n4PJfjdC017986@stora.ogud.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905251941.n4PJfjdC017986@stora.ogud.com> User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: dns-dir@ietf.org Subject: Re: [dns-dir] DNS Early Warn: draft-speakman-looping-issue-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 20:35:43 -0000 On Mon, May 25, 2009 at 03:40:11PM -0400, Olafur Gudmundsson wrote: > They used the word OLSRv2 on 28 lines ah, I missed that, checking RR types only case sensitive. > my script does not require space before or after SRV > for a match, probably a mistake. Not a big deal, I guess we can live with an occasional false alarm. -Peter From peter@denic.de Mon May 25 13:41:32 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7E253A6B8D for ; Mon, 25 May 2009 13:41:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.959 X-Spam-Level: X-Spam-Status: No, score=-5.959 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3yc7chcn4znu for ; Mon, 25 May 2009 13:41:27 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 05CCC3A689B for ; Mon, 25 May 2009 13:41:25 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1M8h0k-0007WY-5F; Mon, 25 May 2009 22:43:06 +0200 Received: from localhost by x27.adm.denic.de with local id 1M8gxE-0008IF-MN; Mon, 25 May 2009 22:39:28 +0200 Date: Mon, 25 May 2009 22:39:28 +0200 From: Peter Koch To: dns-dir@ietf.org Message-ID: <20090525203928.GT13303@x27.adm.denic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Subject: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 20:41:32 -0000 Dear DNS directorate members, our next regular call is scheduled for next Monday, 1st June. This is a holiday around here, but that would not necessarily stop me. However, I have little idea about other countries, so it might be better to re-schedule to 8 June instead. Could you please let me know (private email is OK) your preferences? Potential agenda items: o Administrivia o DNSSEC strategy for the IETF "guidance" asked for by dnsext particpants operational (and other) consequences of multiple algorithms at the root o Role of DNS in service discovery o Recent draft reviews Regards, Peter From pfaltstr@cisco.com Mon May 25 20:47:27 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6319B3A68AE for ; Mon, 25 May 2009 20:47:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.883 X-Spam-Level: X-Spam-Status: No, score=-6.883 tagged_above=-999 required=5 tests=[AWL=-0.584, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7DOGPHnNMou5 for ; Mon, 25 May 2009 20:47:26 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 8221F3A6767 for ; Mon, 25 May 2009 20:47:26 -0700 (PDT) X-Files: PGP.sig : 186 X-IronPort-AV: E=Sophos;i="4.41,248,1241395200"; d="sig'?scan'208";a="164425790" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by sj-iport-3.cisco.com with ESMTP; 26 May 2009 03:49:07 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n4Q3n61n031819; Tue, 26 May 2009 05:49:06 +0200 Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n4Q3n6fp017055; Tue, 26 May 2009 03:49:06 GMT Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 May 2009 05:49:06 +0200 Received: from [192.168.1.129] ([10.61.96.136]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 May 2009 05:49:05 +0200 Message-Id: <39282545-DAEA-4830-BFCC-CBFFCFA06B7F@cisco.com> From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: Peter Koch In-Reply-To: <20090525203928.GT13303@x27.adm.denic.de> Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-109-862056229" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Tue, 26 May 2009 05:49:04 +0200 References: <20090525203928.GT13303@x27.adm.denic.de> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.935.3) X-OriginalArrivalTime: 26 May 2009 03:49:05.0976 (UTC) FILETIME=[EACA7B80:01C9DDB4] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1461; t=1243309746; x=1244173746; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paf@cisco.com; z=From:=20=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20

|Subject:=20Re=3A=20[dns-dir]=20Conf=20call=20on=20June,=20 1st=20or=20June,=208th? |Sender:=20; bh=VBcu147SZcKdAbjArS0wcQ8LiKG9hcAJ4ezj3BUO2+M=; b=QkJMDVwlJW5lwASDXvJ+SuJ5lntrylwGxnF8dcn3cD5Ilr3iYuQ9cEszwN MtFP2DRZ+4K3GieSeGC+ujUILdt+bb692sl8m8w/cImC0zVRTH25tKgK3Q8V cIkGqEQnF+; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: dns directorate Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 03:47:27 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-109-862056229 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On 25 maj 2009, at 22.39, Peter Koch wrote: > Dear DNS directorate members, > > our next regular call is scheduled for next Monday, 1st June. This > is a holiday > around here, but that would not necessarily stop me. However, I have > little > idea about other countries, so it might be better to re-schedule to > 8 June > instead. Could you please let me know (private email is OK) your > preferences? > > Potential agenda items: > > o Administrivia > o DNSSEC strategy for the IETF > "guidance" asked for by dnsext particpants > operational (and other) consequences of multiple algorithms at the > root > o Role of DNS in service discovery > o Recent draft reviews 8th is better for me. And I guess specifically "service discovery" is when you want me there. Right? paf --Apple-Mail-109-862056229 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iD8DBQFKG2awvHlR2X0luNwRAoYTAJ4r0Jo62hIaByiDpFSXD4M6CPCBfQCcCuTk /oBeRgA0nyKws73Ga/2wbzU= =tgLH -----END PGP SIGNATURE----- --Apple-Mail-109-862056229-- From ajs@shinkuro.com Tue May 26 06:29:06 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDA0C3A6B82 for ; Tue, 26 May 2009 06:29:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.855 X-Spam-Level: X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YD6qAYTmZ2Se for ; Tue, 26 May 2009 06:29:03 -0700 (PDT) Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 147B928C1FC for ; Tue, 26 May 2009 06:29:02 -0700 (PDT) Received: from crankycanuck.ca (76-10-166-247.dsl.teksavvy.com [76.10.166.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 235232FE962F; Tue, 26 May 2009 13:28:18 +0000 (UTC) Date: Tue, 26 May 2009 09:28:16 -0400 From: Andrew Sullivan To: Peter Koch Message-ID: <20090526132815.GB5595@shinkuro.com> References: <20090525203928.GT13303@x27.adm.denic.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090525203928.GT13303@x27.adm.denic.de> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 13:29:06 -0000 On Mon, May 25, 2009 at 10:39:28PM +0200, Peter Koch wrote: > Dear DNS directorate members, > > our next regular call is scheduled for next Monday, 1st June. This is a holiday > around here, but that would not necessarily stop me. However, I have little > idea about other countries, so it might be better to re-schedule to 8 June > instead. Could you please let me know (private email is OK) your preferences? On either of the days, I may not have power (I'm having my house rewired), so either one is fine for me. No holiday here. A -- Andrew Sullivan ajs@shinkuro.com Shinkuro, Inc. From liman@autonomica.se Tue May 26 10:18:23 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8758928C24B for ; Tue, 26 May 2009 10:18:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.505 X-Spam-Level: X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, HELO_EQ_SE=0.35] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxRG-JY3tNSD for ; Tue, 26 May 2009 10:18:22 -0700 (PDT) Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by core3.amsl.com (Postfix) with ESMTP id CB7283A6FE9 for ; Tue, 26 May 2009 10:18:21 -0700 (PDT) Received: from home.liman.net (2-1-3-18a.spa.sth.bostream.se [82.182.146.229]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id n4QGN9EW007211; Tue, 26 May 2009 18:23:09 +0200 (MEST) Received: from zaptop.autonomica.net (zaptop.autonomica.net [172.22.1.108]) by home.liman.net (8.14.3/8.14.3) with ESMTP id n4QGN7t8022150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 26 May 2009 18:23:08 +0200 (MEST) Received: from zaptop.autonomica.net (localhost [IPv6:::1]) by zaptop.autonomica.net (8.14.3/8.14.3) with ESMTP id n4QGN621007769; Tue, 26 May 2009 18:23:06 +0200 (CEST) To: Peter Koch References: <20090525203928.GT13303@x27.adm.denic.de> From: Lars-Johan Liman Date: Tue, 26 May 2009 18:23:06 +0200 In-Reply-To: <20090525203928.GT13303@x27.adm.denic.de> (Peter Koch's message of "Mon\, 25 May 2009 22\:39\:28 +0200") Message-ID: <22bppfbzpx.fsf@zaptop.autonomica.net> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 17:18:23 -0000 pk@DENIC.DE: > Dear DNS directorate members, > our next regular call is scheduled for next Monday, 1st June. This is a holiday > around here, but that would not necessarily stop me. However, I have little > idea about other countries, so it might be better to re-schedule to 8 June > instead. Could you please let me know (private email is OK) your preferences? Both are equally bad for me. No holiday, but I will have to leave the ship at 1430 UTC both these days due to other committments. Cheers, /Liman From dromasca@avaya.com Tue May 26 10:38:33 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C6AF28C28F for ; Tue, 26 May 2009 10:38:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.496 X-Spam-Level: X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SfnG7bUgS-X for ; Tue, 26 May 2009 10:38:29 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id B440128C2BB for ; Tue, 26 May 2009 10:38:02 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,253,1241409600"; d="scan'208";a="171968279" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 26 May 2009 13:39:42 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 26 May 2009 13:39:42 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 26 May 2009 19:39:31 +0200 Message-ID: In-Reply-To: <20090525203928.GT13303@x27.adm.denic.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [dns-dir] Conf call on June, 1st or June, 8th? Thread-Index: AcndeW7Sxzvd9T2gQRexuevNJxztzAAr17pA References: <20090525203928.GT13303@x27.adm.denic.de> From: "Romascanu, Dan (Dan)" To: "Peter Koch" , Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 17:38:33 -0000 No holiday here, but I have a semi-conflict on 6/8 starting at 1430 UTC. Dan =20 > -----Original Message----- > From: dns-dir-bounces@ietf.org=20 > [mailto:dns-dir-bounces@ietf.org] On Behalf Of Peter Koch > Sent: Monday, May 25, 2009 11:39 PM > To: dns-dir@ietf.org > Subject: [dns-dir] Conf call on June, 1st or June, 8th? >=20 > Dear DNS directorate members, >=20 > our next regular call is scheduled for next Monday, 1st June.=20 > This is a holiday around here, but that would not necessarily=20 > stop me. However, I have little idea about other countries,=20 > so it might be better to re-schedule to 8 June instead. =20 > Could you please let me know (private email is OK) your preferences? >=20 > Potential agenda items: >=20 > o Administrivia > o DNSSEC strategy for the IETF > "guidance" asked for by dnsext particpants > operational (and other) consequences of multiple algorithms=20 > at the root o Role of DNS in service discovery o Recent draft reviews >=20 > Regards, > Peter > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir >=20 From ogud@ogud.com Tue May 26 11:28:48 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69EEE28C29B for ; Tue, 26 May 2009 11:28:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.177 X-Spam-Level: X-Spam-Status: No, score=-2.177 tagged_above=-999 required=5 tests=[AWL=0.422, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E+Lkfc7acbXN for ; Tue, 26 May 2009 11:28:47 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id D930328C2AC for ; Tue, 26 May 2009 11:28:46 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4QIU1m9032216 for ; Tue, 26 May 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 26 May 2009 14:30:01 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090526_183001_089709.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-moonesamy-smtp-vrfy-ddds-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 18:28:48 -0000 Count: 18 Network Working Group S. Moonesamy Internet Draft May 25, 2009 Intended status: Standards Track Expires: November 24, 2009 SMTP Recipient Address Verification Using the Dynamic Delegation Discovery Service (DDDS) draft-moonesamy-smtp-vrfy-ddds-00.txt Abstract This memo proposes a mechanism based on the Dynamic Delegation Discovery Service (DDDS) which can be used for the verification of SMTP recipient addresses. From ogud@ogud.com Tue May 26 11:28:49 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71E8928C2C5 for ; Tue, 26 May 2009 11:28:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.882 X-Spam-Level: X-Spam-Status: No, score=-1.882 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, J_CHICKENPOX_37=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UkE6DU4XDGPX for ; Tue, 26 May 2009 11:28:48 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 7351128C29D for ; Tue, 26 May 2009 11:28:48 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4QIU27f032259 for ; Tue, 26 May 2009 14:30:02 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 26 May 2009 14:30:02 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090526_183002_044387.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ma-sipping-server-event-package-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 18:28:49 -0000 Count: 24 Network Working Group Tao. Ma Internet-Draft Lichun. Li Intended status: Informational Chunhong. Zhang Expires: Nov 18, 2009 Yang. Ji Xiaofeng. Qiu MINE lab,Beijing University of Posts and Telecommunication May 25, 2009 A SIP server event package for SIP server farm draft-ma-sipping-server-event-package-00 Abstract This document defines the Session Initiation Protocol (SIP) server even package for SIP server farm using the SIP event framework. The SIP server event package allows clients to subscribe to the servers for server information in the server farm, and serves to communicate information with each other. Based on this, an overall view of the SIP server farm is built and delivered to the entity (including SIP phone proxy or other SIP servers) which subscribes and receives the event packages. The view would help failover and load balancing in the server farm. The event notification mechanism of SIP event framework guarantees its adaption to the dynamic changes of server state. We instantiate the usage of SIP server event package in three scenarios: client based failover, DNS based failover, load balancer based load balancing. To be added, we introduce some specific usage in Peer-to-Peer SIP(P2PSIP) and service discovery to expand and explore the potential usage space. Compared with the failover and load balancing mechanisms in traditional SIP, the new SIP event package would apply its explicit and dynamic notification mechanism to improve the efficiency and service availability of SIP server farm. This mechanism using server event package can also be a complementary way for the DNS functionality defined in RFC 3263[RFC 3263] to locate SIP servers. From ogud@ogud.com Tue May 26 11:28:53 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD3B03A6960 for ; Tue, 26 May 2009 11:28:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.183 X-Spam-Level: X-Spam-Status: No, score=-2.183 tagged_above=-999 required=5 tests=[AWL=0.416, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNyuoog6L5D3 for ; Tue, 26 May 2009 11:28:53 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id D8C9F3A709E for ; Tue, 26 May 2009 11:28:52 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4QIU25E032236 for ; Tue, 26 May 2009 14:30:02 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 26 May 2009 14:30:02 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090526_183002_018973.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-speakman-manet-looping-issue-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 18:28:54 -0000 Count: 28 Mobile Ad hoc Networking (MANET) L. Speakman Internet-Draft Research Center for Natural Hazard Intended status: Informational and Disaster Recovery, Niigata Expires: November 25, 2009 University K. Mase Graduate School of Science and Technology, Niigata University May 25, 2009 Routing Loop Issue in Mobile Ad Hoc Networks (MANETs) draft-speakman-manet-looping-issue-00 Abstract This document describes the routing loop and packet looping issues in mobile ad hoc network (MANET) running proactive routing protocols using hop count metric. Mechanisms of loop formation are identified and how the problem of loop formation is exacerbated by the use of Link Layer Notification is described. The effect of the looping packets on the network are shown by comparing against the case where the looping packets are detected and discarded, showing the need for routing loops or looping packets to be dealt with in MANETs. From ogud@ogud.com Tue May 26 11:57:45 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33F743A7092 for ; Tue, 26 May 2009 11:57:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.187 X-Spam-Level: X-Spam-Status: No, score=-2.187 tagged_above=-999 required=5 tests=[AWL=0.412, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JY3xoXUbR7JN for ; Tue, 26 May 2009 11:57:44 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 3CD453A67EE for ; Tue, 26 May 2009 11:57:43 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4QIU2bR032225 for ; Tue, 26 May 2009 14:30:02 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Tue, 26 May 2009 14:30:02 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090526_183002_047485.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-sarikaya-netlmm-lma-dnsdiscovery-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 18:57:45 -0000 Count: 57 Network Working Group B. Sarikaya Internet-Draft F. Xia Expires: November 26, 2009 Huawei USA May 25, 2009 Local Mobile Anchor Discovery Using DNS by Service Name draft-sarikaya-netlmm-lma-dnsdiscovery-00 Abstract This draft defines a Domain Name System (DNS)-based scheme to enable dynamic discovery of a Local Mobility Anchor (LMA) in Proxy Mobile IPv6. DNS Service Resource Record option is used allowing a Mobile Access Gateway (MAG) to request the LMA's Fully Qualified Domain Name (FQDN) and possibly IP address via the DNS response. IPv4 case is also covered. From dromasca@avaya.com Wed May 27 07:59:03 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28EB33A6DA2; Wed, 27 May 2009 07:59:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.496 X-Spam-Level: X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvCEEFSK5Qxa; Wed, 27 May 2009 07:59:02 -0700 (PDT) Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id F14883A6C9A; Wed, 27 May 2009 07:59:01 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,260,1241409600"; d="scan'208";a="162522122" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 27 May 2009 10:59:46 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 27 May 2009 10:59:46 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 27 May 2009 16:59:44 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-crocker-email-arch-13.txt to Proposed Standard Thread-Index: Acne2v4ZP51U9Ry/QZuh00DslX9R2AAAJe3Q From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Evaluation: draft-crocker-email-arch-13.txt to Proposed Standard X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 14:59:03 -0000 =20 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-crocker-email-arch-13.txt Technical Summary Public discussion of the Internet Mail service often lacks common terminology and a common frame of reference for these components and their activities. Having a common reference model and terminology makes a basic difference when talking about problems with the service, changes in policy, or enhancement to the service's functionality. This document offers an enhanced Internet Mail architecture that targets description of the existing service, in order to facilitate clearer and more efficient technical, operations and policy discussions about email. Working Group Summary This document was discussed within the mail community on the mailing lists dedicated to SMTP and the Mail Format. Some of the terms came about as a compromise after long discussions, but rough consensus was achieved on all points. Members of the working groups dealing with IMAP and LEMONADE were aware of this effort, but it was not an appropriate topic for those working groups to place on their charters. There is no other current working group dealing with the mail system in general. Document Quality This document does not create a protocol specification. The acknowledgments indicate that Graham Klyne, Pete Resnick and Steve Atkins provided thoughtful insight on the framework and details of the original drafts. A number of other people have provided additional reviews and insights. Personnel Who is the Document Shepherd for this document? Tony Hansen Who is the Responsible Area Director? Chris Newman and Alexey Melnikov have reviewed this document for IESG. From dromasca@avaya.com Thu May 28 07:33:46 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1B0828C1DC; Thu, 28 May 2009 07:33:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.498 X-Spam-Level: X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oolMNqHKj8Iw; Thu, 28 May 2009 07:33:46 -0700 (PDT) Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 904D83A69A2; Thu, 28 May 2009 07:33:45 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,265,1241409600"; d="scan'208";a="162648131" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 28 May 2009 10:35:22 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 28 May 2009 10:35:21 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 28 May 2009 16:34:54 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-dnsext-dnsproxy-05.txt to BCP Thread-Index: AcnfibhfDB8aBRA9R1Gd8gYiYIqF+AAF7QxA From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Evaluation: draft-ietf-dnsext-dnsproxy-05.txt to BCP X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 14:33:46 -0000 =20 - 'DNS Proxy Implementation Guidelines ' as a BCP This document is the product of the DNS Extensions Working Group.=20 The IESG contact persons are Ralph Droms and Jari Arkko. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dnsext-dnsproxy-05.txt Technical Summary This document is aimed at a target audience that is outside the IETF but implement DNS protocol elements, frequently without much understanding of the DNS protocol. This document gives simple guidance to such people to avoid common mistakes, seen in the field, that cause major interoperabilty issues. Working Group Summary The consensus for this document is real strong. Document Quality This is a high quality draft, that is addressing an important aspect for the interoperabilty of the DNS protocol. Number of vendors that purchase/test DNS gateways have stated that compliance with this document is going to be a purchasing requirement. Personnel Document Shepherd is: Olafur Gudmundsson AD: Ralph Droms RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) From ajs@shinkuro.com Thu May 28 12:42:16 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE0EF3A6F2C for ; Thu, 28 May 2009 12:42:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.849 X-Spam-Level: X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTuU8VUY95VV for ; Thu, 28 May 2009 12:42:16 -0700 (PDT) Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id F2E9F3A6E63 for ; Thu, 28 May 2009 12:42:15 -0700 (PDT) Received: from crankycanuck.ca (external.shinkuro.com [66.92.164.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 91A712FE9637 for ; Thu, 28 May 2009 19:43:58 +0000 (UTC) Date: Thu, 28 May 2009 15:43:57 -0400 From: Andrew Sullivan To: dns-dir@ietf.org Message-ID: <20090528194356.GD755@shinkuro.com> References: <20090525203928.GT13303@x27.adm.denic.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090525203928.GT13303@x27.adm.denic.de> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 19:42:16 -0000 On Mon, May 25, 2009 at 10:39:28PM +0200, Peter Koch wrote: > Dear DNS directorate members, > > our next regular call is scheduled for next Monday, 1st June. Did we nail down when this is going to happen? A -- Andrew Sullivan ajs@shinkuro.com Shinkuro, Inc. From pk@DENIC.DE Thu May 28 23:32:31 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16FF23A6A41 for ; Thu, 28 May 2009 23:32:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.981 X-Spam-Level: X-Spam-Status: No, score=-5.981 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdvmLPXdGYvP for ; Thu, 28 May 2009 23:32:30 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id F386D28C11B for ; Thu, 28 May 2009 23:31:31 -0700 (PDT) Received: from unknown.office.denic.de ([10.122.65.182]) by office.denic.de with esmtp id 1M9veT-0008B6-3k; Fri, 29 May 2009 08:33:13 +0200 Received: by unknown.office.denic.de (Postfix, from userid 501) id 53D57186434; Fri, 29 May 2009 08:33:13 +0200 (CEST) Date: Fri, 29 May 2009 08:33:12 +0200 From: Peter Koch To: Andrew Sullivan Message-ID: <20090529063312.GA46243@unknown.office.denic.de> References: <20090525203928.GT13303@x27.adm.denic.de> <20090528194356.GD755@shinkuro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090528194356.GD755@shinkuro.com> User-Agent: Mutt/1.4.2.1i Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 06:32:31 -0000 On Thu, May 28, 2009 at 03:43:57PM -0400, Andrew Sullivan wrote: > > our next regular call is scheduled for next Monday, 1st June. > > Did we nail down when this is going to happen? of 16 members, feedback has arrived from five, with no real preference. I'd like to wait a few more hours. -Peter From jari.arkko@piuha.net Thu May 28 23:44:07 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D9073A6A5D for ; Thu, 28 May 2009 23:44:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.342 X-Spam-Level: X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOygCCIKR5hO for ; Thu, 28 May 2009 23:44:06 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 4DA333A6B0F for ; Thu, 28 May 2009 23:44:06 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 6448519877B; Fri, 29 May 2009 09:45:49 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 1D1D419869F; Fri, 29 May 2009 09:45:49 +0300 (EEST) Message-ID: <4A1F8497.8050400@piuha.net> Date: Fri, 29 May 2009 09:45:43 +0300 From: Jari Arkko User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= References: <20090525203928.GT13303@x27.adm.denic.de> <39282545-DAEA-4830-BFCC-CBFFCFA06B7F@cisco.com> In-Reply-To: <39282545-DAEA-4830-BFCC-CBFFCFA06B7F@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Peter Koch , dns directorate Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 06:44:07 -0000 8th would be better for me. Jari Patrik Fältström wrote: > On 25 maj 2009, at 22.39, Peter Koch wrote: > >> Dear DNS directorate members, >> >> our next regular call is scheduled for next Monday, 1st June. This is >> a holiday >> around here, but that would not necessarily stop me. However, I have >> little >> idea about other countries, so it might be better to re-schedule to 8 >> June >> instead. Could you please let me know (private email is OK) your >> preferences? >> >> Potential agenda items: >> >> o Administrivia >> o DNSSEC strategy for the IETF >> "guidance" asked for by dnsext particpants >> operational (and other) consequences of multiple algorithms at the root >> o Role of DNS in service discovery >> o Recent draft reviews > > 8th is better for me. And I guess specifically "service discovery" is > when you want me there. Right? > > paf > > ------------------------------------------------------------------------ > > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir > From rdroms@cisco.com Fri May 29 02:03:22 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF8DF3A6EFD for ; Fri, 29 May 2009 02:03:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.529 X-Spam-Level: X-Spam-Status: No, score=-6.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id quq1T1x1HHOW for ; Fri, 29 May 2009 02:03:21 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id CB1903A6F17 for ; Fri, 29 May 2009 02:03:21 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,270,1241395200"; d="scan'208";a="312848919" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-6.cisco.com with ESMTP; 29 May 2009 09:05:05 +0000 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n4T954j3012499; Fri, 29 May 2009 05:05:04 -0400 Received: from bxb-rdroms-8716.cisco.com (bxb-rdroms-8716.cisco.com [10.98.10.87]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n4T954bY024771; Fri, 29 May 2009 09:05:04 GMT Message-Id: <1B01C813-E354-4337-89A2-18F6CDF87A9B@cisco.com> From: Ralph Droms To: Peter Koch In-Reply-To: <20090529063312.GA46243@unknown.office.denic.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 29 May 2009 05:05:04 -0400 References: <20090525203928.GT13303@x27.adm.denic.de> <20090528194356.GD755@shinkuro.com> <20090529063312.GA46243@unknown.office.denic.de> X-Mailer: Apple Mail (2.930.3) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=577; t=1243587904; x=1244451904; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20 |Subject:=20Re=3A=20[dns-dir]=20Conf=20call=20on=20June,=20 1st=20or=20June,=208th? |Sender:=20 |To:=20Peter=20Koch=20; bh=0O/QKcl9IcIznH9i1jV9Q3Ep1Fh8fWQBIVxcsHLNnnI=; b=ON0XiDrUXpMvxkHXUuvDaDCaAP/4XNOZ4QL7+8RgfKeE+tWMPk2yf5FsmE t4pl1VylQBOoKe/K3H1w3bOh6cnAf0oieXWK7SLrnggiwpteotNns0MUCDOU VI8mwOeik0; Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Conf call on June, 1st or June, 8th? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 09:03:22 -0000 June 8 is somewhat better for me. - Ralph On May 29, 2009, at 2:33 AM 5/29/09, Peter Koch wrote: > On Thu, May 28, 2009 at 03:43:57PM -0400, Andrew Sullivan wrote: > >>> our next regular call is scheduled for next Monday, 1st June. >> >> Did we nail down when this is going to happen? > > of 16 members, feedback has arrived from five, with no real > preference. > I'd like to wait a few more hours. > > -Peter > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir From dromasca@avaya.com Fri May 29 04:48:52 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2E173A6C04; Fri, 29 May 2009 04:48:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQ1y9dhY69K4; Fri, 29 May 2009 04:48:51 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 779663A6D46; Fri, 29 May 2009 04:48:51 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,271,1241409600"; d="scan'208";a="172323655" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 29 May 2009 07:49:39 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 May 2009 07:49:39 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 29 May 2009 13:49:37 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PREMINARY Agenda and Package for June 4, 2009 Telechat Thread-Index: Acnf45hnmtVM84d1RSqsAXieslWwFQAb4cOQ From: "Romascanu, Dan (Dan)" To: , , , Subject: [dns-dir] FW: PREMINARY Agenda and Package for June 4, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 11:48:53 -0000 =20 Please find below the preliminary agenda of the 6/4 IESG telechat. Please send me your questions, comments and concerns about the relevant documents and WG charter brought to approval before Wednesday 6/3 COB.=20 Thanks and Regards, Dan --------------------------------------- 2.1 WG Submissions 2.1.1 New Item o draft-ietf-dkim-ssp-10.txt DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)=20 (Proposed Standard) - 1 of 7=20 Note: Document shepherd is Stephen Farrell (stephen.farrell@cs.tcd.ie) =20 Token: Pasi Eronen o draft-ietf-sip-outbound-18.txt Managing Client Initiated Connections in the Session Initiation Protocol=20 (SIP) (Proposed Standard) - 2 of 7=20 Token: Robert Sparks o draft-ietf-mmusic-sdp-capability-negotiation-10.txt SDP Capability Negotiation (Proposed Standard) - 3 of 7=20 Note: Proto Shepherd: Jean-Francois Mule (jf.mule@cablelabs.com)=20 Token: Cullen Jennings o draft-ietf-netlmm-pmip6-ipv4-support-12.txt IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 4 of 7=20 Token: Jari Arkko o draft-ietf-ippm-more-twamp-02.txt More Features for the Two-Way Active Measurement Protocol - TWAMP (Proposed=20 Standard) - 5 of 7=20 Token: Lars Eggert o draft-ietf-dkim-rfc4871-errata-05.txt RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update (Proposed=20 Standard) - 6 of 7=20 Token: Pasi Eronen o draft-ietf-dnsext-dnsproxy-05.txt DNS Proxy Implementation Guidelines (BCP) - 7 of 7=20 Token: Ralph Droms 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-crocker-email-arch-13.txt Internet Mail Architecture (Proposed Standard) - 1 of 1=20 Note: Tony Hansen is document shepherd.=20 Token: Alexey Melnikov 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item o draft-ietf-avt-seed-srtp-11.txt The SEED Cipher Algorithm and Its Use with the Secure Real-time Transport=20 Protocol (SRTP (Informational) - 1 of 2=20 Token: Cullen Jennings o draft-ietf-geopriv-sip-lo-retransmission-02.txt Implications of 'retransmission-allowed' for SIP Location Conveyance (Informational) - 2 of 2=20 Token: Cullen Jennings 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item o draft-ietf-sip-ua-privacy-08.txt UA-Driven Privacy Mechanism for SIP (Informational) - 1 of 1=20 Token: Cullen Jennings 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item o draft-ford-behave-top-06.txt Unintended Consequence of two NAT deployments with Overlapping Address =20 Space (Informational) - 1 of 1=20 Token: Magnus Westerlund 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 1 Token: Magnus Westerlund 4.2.2 Proposed for Approval NONE From pk@DENIC.DE Fri May 29 05:10:03 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50B063A69F6 for ; Fri, 29 May 2009 05:10:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.987 X-Spam-Level: X-Spam-Status: No, score=-5.987 tagged_above=-999 required=5 tests=[AWL=0.262, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWI4SALdAXF2 for ; Fri, 29 May 2009 05:10:02 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 8AC783A688C for ; Fri, 29 May 2009 05:10:02 -0700 (PDT) Received: from unknown.office.denic.de ([10.122.65.182]) by office.denic.de with esmtp id 1MA0uI-0003QR-Cz; Fri, 29 May 2009 14:09:54 +0200 Received: by unknown.office.denic.de (Postfix, from userid 501) id 4EF3D18685A; Fri, 29 May 2009 14:09:54 +0200 (CEST) Date: Fri, 29 May 2009 14:09:53 +0200 From: Peter Koch To: dns-dir@ietf.org Message-ID: <20090529120953.GC46594@unknown.office.denic.de> References: <20090525203928.GT13303@x27.adm.denic.de> <20090528194356.GD755@shinkuro.com> <20090529063312.GA46243@unknown.office.denic.de> <1B01C813-E354-4337-89A2-18F6CDF87A9B@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1B01C813-E354-4337-89A2-18F6CDF87A9B@cisco.com> User-Agent: Mutt/1.4.2.1i Subject: [dns-dir] Moved [Re: Conf call on June, 1st or June, 8th?] X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 12:10:03 -0000 On Fri, May 29, 2009 at 05:05:04AM -0400, Ralph Droms wrote: > June 8 is somewhat better for me. with this additional feedback and the time left before weekend starts on this side of the Atlantic, I'd suggest we re-schedule the meeting to Monday, 8 June, 14:00 UTC Best regards, Peter From ogud@ogud.com Fri May 29 08:39:50 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63C273A6C68 for ; Fri, 29 May 2009 08:39:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.179 X-Spam-Level: X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5 tests=[AWL=0.420, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExcxBRh4btfZ for ; Fri, 29 May 2009 08:39:49 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 1A24F3A6B8C for ; Fri, 29 May 2009 08:39:48 -0700 (PDT) Received: from Puki.ogud.com (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4TFfA34030627 for ; Fri, 29 May 2009 11:41:11 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200905291541.n4TFfA34030627@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 29 May 2009 11:39:18 -0400 To: From: Olafur Gudmundsson In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: Re: [dns-dir] FW: PREMINARY Agenda and Package for June 4, 2009 Telechat X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 15:39:50 -0000 None of the drafts show up in DNS-early-warning DB. Olafur At 07:49 29/05/2009, Romascanu, Dan (Dan) wrote: > >Please find below the preliminary agenda of the 6/4 IESG telechat. >Please send me your questions, comments and concerns about the relevant >documents and WG charter brought to approval before Wednesday 6/3 COB. > >Thanks and Regards, > >Dan > >--------------------------------------- > > > >2.1 WG Submissions >2.1.1 New Item > o draft-ietf-dkim-ssp-10.txt > DomainKeys Identified Mail (DKIM) Author Domain Signing Practices >(ADSP) > (Proposed Standard) - 1 of 7 > Note: Document shepherd is Stephen Farrell >(stephen.farrell@cs.tcd.ie) > > Token: Pasi Eronen > o draft-ietf-sip-outbound-18.txt > Managing Client Initiated Connections in the Session Initiation >Protocol > (SIP) (Proposed Standard) - 2 of 7 > Token: Robert Sparks > o draft-ietf-mmusic-sdp-capability-negotiation-10.txt > SDP Capability Negotiation (Proposed Standard) - 3 of 7 > Note: Proto Shepherd: Jean-Francois Mule (jf.mule@cablelabs.com) > Token: Cullen Jennings > o draft-ietf-netlmm-pmip6-ipv4-support-12.txt > IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 4 of 7 > Token: Jari Arkko > o draft-ietf-ippm-more-twamp-02.txt > More Features for the Two-Way Active Measurement Protocol - TWAMP >(Proposed > Standard) - 5 of 7 > Token: Lars Eggert > o draft-ietf-dkim-rfc4871-errata-05.txt > RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update >(Proposed > Standard) - 6 of 7 > Token: Pasi Eronen > o draft-ietf-dnsext-dnsproxy-05.txt > DNS Proxy Implementation Guidelines (BCP) - 7 of 7 > Token: Ralph Droms > >2.1.2 Returning Item >NONE > >2.2 Individual Submissions >2.2.1 New Item > o draft-crocker-email-arch-13.txt > Internet Mail Architecture (Proposed Standard) - 1 of 1 > Note: Tony Hansen is document shepherd. > Token: Alexey Melnikov > >2.2.2 Returning Item >NONE > >3. Document Actions > >3.1 WG Submissions > Reviews should focus on these questions: "Is this document a >reasonable > contribution to the area of Internet engineering which it >covers? If > not, what changes would make it so?" > >3.1.1 New Item > o draft-ietf-avt-seed-srtp-11.txt > The SEED Cipher Algorithm and Its Use with the Secure Real-time >Transport > Protocol (SRTP (Informational) - 1 of 2 > Token: Cullen Jennings > o draft-ietf-geopriv-sip-lo-retransmission-02.txt > Implications of 'retransmission-allowed' for SIP Location Conveyance > > (Informational) - 2 of 2 > Token: Cullen Jennings > >3.1.2 Returning Item >NONE > >3.2 Individual Submissions Via AD > Reviews should focus on these questions: "Is this document a >reasonable > contribution to the area of Internet engineering which it >covers? If > not, what changes would make it so?" > >3.2.1 New Item > o draft-ietf-sip-ua-privacy-08.txt > UA-Driven Privacy Mechanism for SIP (Informational) - 1 of 1 > Token: Cullen Jennings > >3.2.2 Returning Item >NONE >3.3 Independent Submissions Via RFC Editor > The IESG will use RFC 3932 responses: 1) The IESG has not > found any conflict between this document and IETF work; 2) The > IESG thinks that this work is related to IETF work done in WG > , but this does not prevent publishing; 3) The IESG thinks > that publication is harmful to work in WG and recommends > not publishing at this time; 4) The IESG thinks that this > document violates the IETF procedures for and should > therefore not be published without IETF review and IESG > approval; 5) The IESG thinks that this document extends an > IETF protocol in a way that requires IETF review and should > therefore not be published without IETF review and IESG >approval. > > The document shepherd must propose one of these responses in > the Data Tracker note and supply complete text in the IESG > Note portion of the write-up. The Area Director ballot positions > indicate consensus with the response proposed by the > document shepherd. > > Other matters may be recorded in comments, and the comments will > be passed on to the RFC Editor as community review of the >document. > > >3.3.1 New Item > o draft-ford-behave-top-06.txt > Unintended Consequence of two NAT deployments with Overlapping >Address > > Space (Informational) - 1 of 1 > Token: Magnus Westerlund > >3.3.2 Returning Item >NONE > >4. Working Group Actions >4.1 WG Creation >4.1.1 Proposed for IETF Review > NONE >4.1.2 Proposed for Approval > NONE >4.2 WG Rechartering >4.2.1 Under evaluation for IETF Review > o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 1 > Token: Magnus Westerlund >4.2.2 Proposed for Approval > NONE > > >_______________________________________________ >dns-dir mailing list >dns-dir@ietf.org >https://www.ietf.org/mailman/listinfo/dns-dir From ogud@ogud.com Fri May 29 11:29:48 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CD9D3A6774 for ; Fri, 29 May 2009 11:29:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.175 X-Spam-Level: X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[AWL=0.424, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q24IuD5U7ty6 for ; Fri, 29 May 2009 11:29:47 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id AD2433A68CF for ; Fri, 29 May 2009 11:29:47 -0700 (PDT) Received: from localhost (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.3/8.14.3) with ESMTP id n4TIU0VN032702 for ; Fri, 29 May 2009 14:30:00 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Fri, 29 May 2009 14:30:00 -0400 X-Mailer: Perl script "early-new.pl" using Mail::Sender 0.8.16 by Jenda Krynicky, Czechlands running on localhost (127.0.0.1) under account "idmbox" Message-ID: <20090529_183000_068173.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-ietf-netlmm-lma-discovery-00.txt X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 18:29:48 -0000 Count: 25 Network-based Localized Mobility J. Korhonen Management (NetLMM) Nokia Siemens Networks Internet-Draft V. Devarapalli Intended status: Informational WiChorus Expires: November 26, 2009 May 25, 2009 LMA Discovery for Proxy Mobile IPv6 draft-ietf-netlmm-lma-discovery-00.txt Abstract Large Proxy Mobile IPv6 deployments would benefit from a functionality, where a Mobile Access Gateway could dynamically discover a Local Mobility Anchor for a Mobile Node attaching to a Proxy Mobile IPv6 domain. The purpose of the dynamic discovery functionality is to reduce the amount of static configuration in the Mobile Access Gateway. This specification describes a number of possible dynamic Local Mobility Anchor discovery solutions. From dromasca@avaya.com Sun May 31 03:21:37 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CC2428C0FF; Sun, 31 May 2009 03:21:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.497 X-Spam-Level: X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qwKRdMGTKVB; Sun, 31 May 2009 03:21:36 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 12F193A6836; Sun, 31 May 2009 03:21:35 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,278,1241409600"; d="scan'208";a="172470599" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 31 May 2009 06:23:20 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 31 May 2009 06:23:20 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 31 May 2009 12:22:58 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Charter Update for Geopriv WG Thread-Index: Acnf9osOnnQG6QX+TWyrRlHzOS1mgwB4yYRw From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Charter Update for Geopriv WG X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 10:21:37 -0000 =20 Please let me know if you have any comments or concerns.=20 Thanks and Regards, Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Cullen Jennings Sent: Friday, May 29, 2009 3:44 AM To: IESG IESG Cc: Richard Barnes Subject: Charter Update for Geopriv WG bcc to iesg-secretary Can you please put this Charter on the agenda for the next IESG call. =20 It should go in the "4.1.1 Proposed for IETF Review" section. ---------------------------- The IETF has recognized that many applications are emerging that require geographic and civic location information about resources and entities, and that the representation and transmission of that information has significant privacy and security implications. We have created a suite of protocols that allow such applications to represent and transmit such location objects and to allow users to express policies on how these representations are exposed and used. The IETF has also begun working on creating applications that use these capabilities, for emergency services, general real-time communication, and other usages. The GEOPRIV working group is chartered to continue to develop and refine representations of location in Internet protocols, and to analyze the authorization, integrity, and privacy requirements that must be met when these representations of location are created, stored, and used. The group will create and refine mechanisms for the transmission of these representations that address the requirements that have been identified. The working group will work with other IETF working groups and other standards development organizations that are building applications that use location information to ensure that the requirements are well understood and met, and that no additional security or privacy issues related to location are left unaddressed as these location information is incorporated into other protocols. It remains a goal of the GEOPRIV working group to deliver specifications of broad applicability that will become mandatory to implement for IETF protocols that are location aware. This working group will not develop location-determining technology. =20 However, the IETF acknowledges that information used in the location- determination process will in some cases need to be carried over the Internet. Where necessary, this working group will develop protocols or protocol extensions to encode location-determination data structures defined elsewhere. This working group will not develop technologies to directly address any particular regulatory requirements (e.g. 9-1-1). The group will continue to coordinate with any other IETF entities that are working on those problems to ensure the technologies created here meet the needs of those entities, and that the authorization, integrity, and privacy requirements on the mechanisms provided by these technologies continue to be met. Goals and Milestones Done Discuss initial geopriv scenarios and application requirements i- d's Done Discuss initial geographic location privacy and security requirements i-d. Done Initial i-d on geographic information protocol design, including privacy and security techniques. Done Review charter and initial i-ds with AD, and have IESG consider rechartering if necessary. Done Submit geopriv scenarios and application requirements to IESG for publication as Informational RFCs Done Submit security/privacy requirements I-D to IESG for publication as Informational RFC. Done Submit PIDF-LO basic geopriv object draft as a PS Done Initial Common Rules base object draft Done Initial Common Rules GEOPRIV object draft Done Submit DHCP Civil draft as a PS Done Resubmit Conveying Location Objects in RADIUS and Diameter to =20 the IESG for publication as PS Done Submit Additional Civic PIDF-LO types (updating 4119) to the =20 IESG for publication as PS Done Submit minimal HTTP based protocol satisfying baseline =20 requirements specified in the Layer 7 Location Conveyance Protocol Problem Statement and Requirements to the IESG for publication as PS Done Submit PIDF-LO Usage Clarifications and Recommendations =20 (updating 4119) to the IESG for publication as PS Done Submit Layer 7 Location Conveyance Protocol Problem Statement =20 and Requirements to the IESG for publication as Informational Done Submit recommendations for representing civic addresses in =20 PIDF-LO to the IESG for publication as BCP Done Submit Recommendations for Retransmission in SIP Location =20 Conveyance to the IESG for publication as Informational Done Submit Requirements for Location by Reference Protocols to =20 the IESG for publication as Informational Done Submit a LIS Discovery Mechanism to the IESG for publication as a PS Jun 2009 Resubmit Geolocation Policy to the IESG for publication as PS Sep 2009 Submit an draft for DHCP geodetic location to the IESG for publication as PS to obsolete 3825 Sep 2009 Submit an Architecture for Location and Location Privacy to the IESG for publication as Informational Dec 2009 Submit a URI scheme for directly expressing geodetic location to the IESG for publication as PS Dec 2009 Submit a DHCP Option for a Location Uniform Resource Identifier (URI) to the IESG for publication as PS Dec 2009 Submit a Document Format for Filtering and Reporting PIDF-LO Location Notifications to the IESG for publication as PS From dromasca@avaya.com Sun May 31 03:41:43 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9876628C16B; Sun, 31 May 2009 03:41:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.498 X-Spam-Level: X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BgtirjpCZGcm; Sun, 31 May 2009 03:41:42 -0700 (PDT) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 194A128C1AF; Sun, 31 May 2009 03:41:27 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,278,1241409600"; d="scan'208";a="172471155" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 31 May 2009 06:43:12 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 31 May 2009 06:43:11 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 31 May 2009 12:43:00 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Internal WG Review: Recharter of Point-to-Point Protocol Extensions (pppext) Thread-Index: AcngmE3qjL7iPgEURy+T2eCe84QNwgBRDPGg From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Internal WG Review: Recharter of Point-to-Point Protocol Extensions (pppext) X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 10:41:43 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Friday, May 29, 2009 11:00 PM To: iesg@ietf.org; iab@iab.org; james.d.carlson@sun.com Subject: Internal WG Review: Recharter of Point-to-Point Protocol Extensions (pppext)=20 A new charter for the Point-to-Point Protocol Extensions working group (pppext) in the Internet Area of the IETF is being considered. The draft charter is provided below for your review and comment. Review time is one week. The IETF Secretariat Point-to-Point Protocol Extensions (pppext) -------------------------------------------- Last Modified: 2009-05-29 Additional information is available at tools.ietf.org/wg/pppext Chair(s): James Carlson Internet Area Director(s): Ralph Droms Jari Arkko Internet Area Advisor: Jari Arkko Mailing Lists: General Discussion: pppext@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/pppext In Body: subscribe Archive: http://www.ietf.org/mail-archive/web/pppext/index.html Description of Working Group: The Point-to-Point Protocol (PPP, RFC 1661) is a mature protocol with a large number of subprotocols, encapsulations and other extensions. The PPPEXT working exists to provide a forum for asking clarifications about the existing specifications and to defend against enhancements of questionable value. The group is not expected to create new specifications, and if a need for such work comes up, a recharter is required. The group may, however, advance existing specifications to the next level in the standards track, if a need for that comes up. Similarly, the group may classify existing specifications as Historic where this is appropriate. Goals and Milestones: Done Advance SDL draft to Experimental Done Add VLAN support to BCP (RFC 1638) and recycle at Proposed=20 Standard From dromasca@avaya.com Sun May 31 08:04:45 2009 Return-Path: X-Original-To: dns-dir@core3.amsl.com Delivered-To: dns-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4E1928C0F9; Sun, 31 May 2009 08:04:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.195 X-Spam-Level: X-Spam-Status: No, score=-2.195 tagged_above=-999 required=5 tests=[AWL=-0.196, BAYES_00=-2.599, J_CHICKENPOX_13=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOHapKI6hwJ7; Sun, 31 May 2009 08:04:44 -0700 (PDT) Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 034CE3A6EA3; Sun, 31 May 2009 08:04:43 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,279,1241409600"; d="scan'208";a="162891984" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 31 May 2009 11:06:28 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 May 2009 11:06:27 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 31 May 2009 17:06:05 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Internal WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave) Thread-Index: AcnfyyZQjbURAxzETJWn8JgyexRBTQCNhufw From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Internal WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave) X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 15:04:45 -0000 =20 Please find below the proposal for re-chartering behave. Let me know before Wednesday 6/3 if there are any questions or concerns.=20 Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Thursday, May 28, 2009 10:31 PM To: iesg@ietf.org; iab@iab.org; dwing@cisco.com; dthaler@microsoft.com Subject: Internal WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave)=20 A new charter for the Behavior Engineering for Hindrance Avoidance working group (behave) in the Transport Area of the IETF is being considered. The draft charter is provided below for your review and comment. Review time is one week. The IETF Secretariat Behavior Engineering for Hindrance Avoidance (behave) ----------------------------------------------------- Last Modified: 2009-05-27 Current Status: Active Working Group Chair(s): Dan Wing Dave Thaler Transport Area Director(s): Magnus Westerlund Lars Eggert Transport Area Advisor: Magnus Westerlund Mailing Lists: General Discussion: behave@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/behave Archive: http://www.ietf.org/mail-archive/web/behave Description of Working Group: The behavior of NATs varies from one implementation to another. As a result it is very difficult for applications to predict or discover the behavior of these devices. Predicting and/or discovering the behavior of NATs is important for designing application protocols and NAT traversal techniques that work reliably in existing networks. This situation is especially problematic for end- to-end applications where one or both end-points are behind a NAT, such as multiuser games, interactive multimedia and P2P download. The working group documents best current practices to enable NATs to function in as deterministic a fashion as possible. The NAT behavior practices will be application independent. This has already completed for UDP, TCP, DCCP, Multicast and ICMP. It continues with SCTP and any additional protocol deemed necessary to handle. The WG has documented approaches for characterizing and testing NAT devices. BEHAVE will develop protocol-independent toolkits usable by application protocols for NAT traversal. The WG has already produced an update of the binding discovery protocol STUN. It will now produce a relay protocol that focuses on security that is usable with both IPv4 and IPv6, and capable of relaying between the two IP versions. The goal of this work is to encourage migration to IPv6. To support deployments where communicating hosts require using different address families (IPv4 or IPv6), address family translation is needed to establish communication. In BEHAVE's specification work on this topic it will coordinate with the V6ops WG on requirements and operational considerations. "An IPv4 network" or "an IPv6 network" in the descriptions below refer to a network with a clearly identifiable administrative domain (e.g., an enterprise campus network, a mobile operator's cellular network, a residential subscriber network, etc.). It will also be that network that deploys the necessary equipment for translation. The BEHAVE WG will design solutions for the following six translation scenarios; other scenarios are out of scope: 1. An IPv6 network to IPv4 Internet, i.e. perform translation between IPv4 and IPv6 for packets in uni- or bi-directional flows that are initiated from an IPv6 host towards an IPv4 host. The translator function is intended to service a specific IPv6 network of arbitary size. Port translation is necessary on the IPv4 side for efficient IPv4 address usage. 2. IPv6 Internet to an IPv4 network, i.e. perform translation between IPv4 and IPv6 for packets in uni- or bi-directional flows that are initiated from an IPv6 host towards an IPv4 host. The translator function services is intended to service a specific IPv4 network using either private or public IPv4 addresses. Because this scenario has different constraints compared to (1), e.g. the IPv4 hosts that are to be reachable over IPv6 can be enumerated. The WG should attempt to design a simpler solution with less impact on applications. 3. An IPv4 network to IPv6 Internet, i.e. perform translation between IPv4 and IPv6 for packets in uni- or bi-directional flows that are initiated from an IPv4 host towards an IPv6 host. The translator function is intended to service a specific IPv4 network using either public or private IPv4 address space. 4. IPv4 Internet to an IPv6 network, i.e. perform translation between IPv4 and IPv6 for packets in uni- or bi-directional flows that are initiated from an IPv4 host towards an IPv6 host. The translator function is intended to service a specific IPv6 network where selected IPv6 hosts and services are to be reachable. 5. An IPv6 network to an IPv4 network, i.e., perform translation between IPv6 and IPv4 for packets in uni- or bi-directional flows that are initiated from an IPv6 host towards an IPv4 host. The translation function is intended to service a specific IPv6 network of arbitrary size and a specific IPv4 network of arbitrary size (neither of which are the Internet). 6. An IPv4 network to an IPv6 network, i.e., perform translation between IPv4 and IPv6 for packets in uni- or bi-directional flows that are initiated from an IPv4 host towards an IPv6 host. The translation function is intended to service a specific IPv6 network of arbitrary size and a specific IPv4 network of arbitrary size (neither of which are the Internet). All translation solutions shall be capable of handling flows using TCP, UDP, DCCP, and SCTP, unless they prevent a timely completion of the work item. The fundamental parts of ICMP are also required to work. Additional protocols directly on top of IP may be supported. Translation mechanisms must handle IP fragmentation. The translators should support multicast traffic and its control traffic (IGMP and MLD) across them, both Single Source Multicast (SSM) and Any Source Multicast (ASM). However, the WG may determine that it becomes too complex or too difficult to realize with maintained functionality, for some or all cases of multicast functionality. Translation mechanisms cannot transparently support protocols that embed network addresses within their protocol messages without application level gateways (ALGs). Because ALGs have security issues (like blocking usage of TLS), are error prone and brittle, and hinder application development, the usage of ALGs in the defined translators should be avoided. Instead application developers will need to be aware and use mechanisms that handle the address family translation. ALGs may be considered only for the most crucial of legacy applications. DNS is a crucial part in making a large number of applications work across a translator. Thus the solution to the above translation cases shall include recommendations for DNS. If additional DNS functionality is needed, it may be developed. Any DNS extensions must be developed together with the DNSEXT WG, including issuing a joint WG last call for any documents. The WG needs to determine the best method for providing address space to a translator in the different deployment cases and documenting the pros and cons of the suggested approaches. The WG is to seek input from the Routing, Operations and Internet areas. Solutions may solve more than one of the cases, however timely delivery is more important than a unified solution. Goals and Milestones: Done Submit BCP that defines unicast UDP behavioral requirements for NATs to IESG Done Submit a BCP that defines TCP behavioral requireents for NATs to IESG Done Submit a BCP that defines ICMP behavioral requirements for NATs to IESG Done Submit informational that discusses current NAT traversal techniques used by applications Done Submit BCP that defines multicast UDP Done Submit revision of RFC 3489 to IESG behavioral requirements for NATs to IESG Done Submit informational document for rfc3489bis test vectors Done Submit experimental document that describes how an application can determine the type of NAT it is behind Done Submit BCP document for DCCP NAT behavior Jun 2009 Submit BCP document for SCTP NAT behavior Done Submit standards-track relay protocol Done Determine relative prioritization of the four translation cases. =20 Sep 2009 Submit standards-track document for relaying of a TCP bytestream Jun 2009 Submit standard-track document of an IPv6 relay protocol to IESG Done Determine what solutions(s) and components are needed to solve each of the four cases. Create new milestones for the solution(s) and the components. Jul 2009 Submit standards-track TURN-URI document Sep 2009 Submit informational for framework for IPv6/IPv4 translation document Sep 2009 Submit standards-track stateless IPv6/IPv4 translation document Sep 2009 Submit standards-track stateful IPv6/IPv4 translation document Sep 2009 Submit standards-track DNS rewriting for IPv6/IPv4 translation document Nov 2009 Submit standards-track FTP ALG for IPv6/IPv4 translation document Nov 2009 Submit standards-track IPv6 prefix for IPv6/IPv4 translator document Mar 2010 Submit BCP large scale NAT requirements document=20