From dromasca@avaya.com Fri Apr 3 02:04: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 CD94A3A6968; Fri, 3 Apr 2009 02:04:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.507 X-Spam-Level: X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 eGwB7aZWSH85; Fri, 3 Apr 2009 02:04:21 -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 9CAC23A69DB; Fri, 3 Apr 2009 02:04:21 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.39,318,1235970000"; d="scan'208";a="166838090" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Apr 2009 05:05:23 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 03 Apr 2009 05:05:22 -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, 3 Apr 2009 11:05:20 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for April 9, 2009 Telechat Thread-Index: Acmz3y3SSoSLlC+ORC+4RbrHrPD4QwAW3lGw From: "Romascanu, Dan (Dan)" To: , "MIB Doctors (E-mail)" , , Subject: [dns-dir] FW: PRELIMINARY Agenda and Package for April 9, 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, 03 Apr 2009 09:04:22 -0000 Please find below the preliminary agenda of the 4/9 telechat. Please send your comments and concerns until Wednesday 4/8 the latest. Also note that several Working Groups are on the agenda of the telechat for discussions and approval.=20 Please copy Ron on your mails. I will be missing this telechat because of a short vacation (4/7 to 4/12).=20 Dan 2.1 WG Submissions 2.1.1 New Item o draft-ietf-nsis-ntlp-19.txt GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 9=20 Note: Please check your comment field so that it doesn't contain old text!=20 RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please indicate in the comment field that you have performed this re-evaluation.=20 Pleas also include some motivation behind your decision.=20 Token: Magnus Westerlund o draft-ietf-behave-turn-13.txt Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) (Proposed Standard) - 2 of 9=20 Token: Magnus Westerlund o draft-ietf-mpls-ldp-capabilities-03.txt LDP Capabilities (Proposed Standard) - 3 of 9=20 Token: Ross Callon o draft-ietf-kitten-gssapi-channel-bindings-06.txt Clarifications and Extensions to the GSS-API for the Use of Channel=20 Bindings (Proposed Standard) - 4 of 9=20 Note: proto writeup received...=20 Token: Tim Polk o draft-ietf-softwire-security-requirements-07.txt Softwire Security Analysis and Requirements (Proposed Standard) - 5 of 9=20 Token: ? o draft-ietf-ntp-ntpv4-proto-11.txt Network Time Protocol Version 4 Protocol And Algorithms Specification (Proposed Standard) - 6 of 9=20 Token: ? o draft-ietf-ntp-ntpv4-mib-05.txt Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)=20 (Proposed Standard) - 7 of 9=20 Token: ? o draft-ietf-ccamp-path-key-ero-04.txt RSVP Extensions for Path Key Support (Proposed Standard) - 8 of 9=20 Token: Ross Callon o draft-ietf-pce-global-concurrent-optimization-10.txt Path Computation Element Communication Protocol (PCEP) Requirements and=20 Protocol Extensions In Support of Global Concurrent Optimization (Proposed=20 Standard) - 9 of 9=20 Token: Ross Callon 2.1.2 Returning Item o draft-ietf-ippm-duplicate-07.txt A One-Way Packet Duplication Metric (Proposed Standard) - 1 of 1=20 Token: Lars Eggert 2.2 Individual Submissions 2.2.1 New Item NONE 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-lemonade-streaming-10.txt Streaming Internet Messaging Attachments (Informational) - 1 of 1=20 Note: Glenn Parsons is document shepherd=20 Token: Alexey Melnikov 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 o draft-despres-6rd-02.txt IPv6 Rapid Deployment on IPv4 infrastructures (6rd) (Informational) - 1 of=20 1=20 Token: Jari Arkko 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Multiple Interfaces (mif) - 1 of 1 Token: Jari Arkko 4.1.2 Proposed for Approval o Locator/ID Separation Protocol (lisp) - 1 of 3 Token: Jari Arkko o Session Initiation Protocol Core (sipcore) - 2 of 3 Token: Cullen Jennings o Dispatch (dispatch) - 3 of 3 Token: Cullen Jennings From ogud@ogud.com Fri Apr 3 05:25: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 7B1443A6946 for ; Fri, 3 Apr 2009 05:25:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.475 X-Spam-Level: X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 JUfB9fzEiBSN for ; Fri, 3 Apr 2009 05:25:41 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 075B93A6862 for ; Fri, 3 Apr 2009 05:25:40 -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 n33CQfI5003753 for ; Fri, 3 Apr 2009 08:26:41 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200904031226.n33CQfI5003753@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 03 Apr 2009 08:26:33 -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: PRELIMINARY Agenda and Package for April 9, 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, 03 Apr 2009 12:25:42 -0000 None of the drafts show up in the DNS-early waring DB. The charter for Lisp should be commented on by people that know something about both DNS and Routing. Olafur At 05:05 03/04/2009, Romascanu, Dan (Dan) wrote: >Please find below the preliminary agenda of the 4/9 telechat. Please >send your comments and concerns until Wednesday 4/8 the latest. Also >note that several Working Groups are on the agenda of the telechat for >discussions and approval. > >Please copy Ron on your mails. I will be missing this telechat because >of a short vacation (4/7 to 4/12). > >Dan > > > > >2.1 WG Submissions >2.1.1 New Item > o draft-ietf-nsis-ntlp-19.txt > GIST: General Internet Signalling Transport (Proposed Standard) - 1 >of >9 > Note: Please check your comment field so that it doesn't contain old >text! > RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please > > indicate in the comment field that you have performed this >re-evaluation. > Pleas also include some motivation behind your decision. > Token: Magnus Westerlund > o draft-ietf-behave-turn-13.txt > Traversal Using Relays around NAT (TURN): Relay Extensions to >Session > > Traversal Utilities for NAT (STUN) (Proposed Standard) - 2 of 9 > Token: Magnus Westerlund > o draft-ietf-mpls-ldp-capabilities-03.txt > LDP Capabilities (Proposed Standard) - 3 of 9 > Token: Ross Callon > o draft-ietf-kitten-gssapi-channel-bindings-06.txt > Clarifications and Extensions to the GSS-API for the Use of Channel > Bindings (Proposed Standard) - 4 of 9 > Note: proto writeup received... > Token: Tim Polk > o draft-ietf-softwire-security-requirements-07.txt > Softwire Security Analysis and Requirements (Proposed Standard) - 5 >of >9 > Token: ? > o draft-ietf-ntp-ntpv4-proto-11.txt > Network Time Protocol Version 4 Protocol And Algorithms >Specification > > (Proposed Standard) - 6 of 9 > Token: ? > o draft-ietf-ntp-ntpv4-mib-05.txt > Definitions of Managed Objects for Network Time Protocol Version 4 >(NTPv4) > (Proposed Standard) - 7 of 9 > Token: ? > o draft-ietf-ccamp-path-key-ero-04.txt > RSVP Extensions for Path Key Support (Proposed Standard) - 8 of 9 > Token: Ross Callon > o draft-ietf-pce-global-concurrent-optimization-10.txt > Path Computation Element Communication Protocol (PCEP) Requirements >and > Protocol Extensions In Support of Global Concurrent Optimization >(Proposed > Standard) - 9 of 9 > Token: Ross Callon > >2.1.2 Returning Item > o draft-ietf-ippm-duplicate-07.txt > A One-Way Packet Duplication Metric (Proposed Standard) - 1 of 1 > Token: Lars Eggert > > >2.2 Individual Submissions >2.2.1 New Item >NONE >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-lemonade-streaming-10.txt > Streaming Internet Messaging Attachments (Informational) - 1 of 1 > Note: Glenn Parsons is document shepherd > Token: Alexey Melnikov > >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 > o draft-despres-6rd-02.txt > IPv6 Rapid Deployment on IPv4 infrastructures (6rd) (Informational) >- >1 of > 1 > Token: Jari Arkko > >3.3.2 Returning Item >NONE > >4. Working Group Actions >4.1 WG Creation >4.1.1 Proposed for IETF Review > o Multiple Interfaces (mif) - 1 of 1 > Token: Jari Arkko >4.1.2 Proposed for Approval > o Locator/ID Separation Protocol (lisp) - 1 of 3 > Token: Jari Arkko > o Session Initiation Protocol Core (sipcore) - 2 of 3 > Token: Cullen Jennings > o Dispatch (dispatch) - 3 of 3 > Token: Cullen Jennings >_______________________________________________ >dns-dir mailing list >dns-dir@ietf.org >https://www.ietf.org/mailman/listinfo/dns-dir From dromasca@avaya.com Sun Apr 5 08:53: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 470073A677D; Sun, 5 Apr 2009 08:53:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.507 X-Spam-Level: X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 55SyoSl2DZSl; Sun, 5 Apr 2009 08:53:51 -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 7F1143A6A11; Sun, 5 Apr 2009 08:53:50 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.39,326,1235970000"; d="scan'208";a="142295078" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Apr 2009 11:54:52 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 05 Apr 2009 11:54:51 -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, 5 Apr 2009 17:54:32 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Internal WG Review: Multiple InterFaces (mif) Thread-Index: Acmz1F1hFAnboVueQ+yBKi2Ssry2+gCMmUIg From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Internal WG Review: Multiple InterFaces (mif) 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, 05 Apr 2009 15:53:52 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Thursday, April 02, 2009 11:47 PM To: iesg@ietf.org; iab@iab.org Subject: Internal WG Review: Multiple InterFaces (mif)=20 A new IETF working group is being considered in the Internet Area. The draft charter for this working group is provided below for your review and comment. Review time is one week. The IETF Secretariat Multiple InterFaces (mif) ------------------------------------------------ Last Modified: 2009-04-02 Current Status: Proposed Working Group Chair(s): TBD Internet Area Director(s): Ralph Droms Jari Arkko Internet Area Advisor: TBD Mailing Lists: General Discussion: mif@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/mif Archive: http://www.ietf.org/mail-archive/web/mif Description of Working Group: Many hosts have the ability to connect to multiple networks simultaneously. This can happen over multiple physical network interfaces, a combination of physical and virtual interfaces (VPNs or tunnels), or even through multiple default routers being on the same link. For instance, current laptops and smartphones typically have multiple access network interfaces. A host connected to multiple networks has to make decisions about default router selection, address selection, DNS server selection, choice of interface for packet transmission, and the treatment of configuration information received from the various networks. Some configuration objects are global to the node, some are local to the interface, and some are related to a particular prefix. Various issues arise when multiple configuration objects that are global to the node are received on different interfaces. At best, decisions about these matters have an efficiency effect. At worst, they have more significant effects such as security impacts, or even lead to communication not being possible at all. A number of operating systems have implemented various techniques to deal with multiple interfaces. Some devices employ only one interface at a time and some allow per-host configuration of preferences between the interfaces but still use just one at a time. Other systems allow per-application preferences or implement sophisticated policy managers that can be configured by users or controlled externally. The purpose of the MIF working group is to describe the issues surrounding the use of multiple interfaces on hosts, document existing practice, and make recommendations about best current practice. The WG shall employ and refer to existing IETF work in this area, including, for instance, strong/weak models (RFC 1122), address selection (RFC 3484), DHCP mechanisms, Router Advertisement mechanisms, and DNS recommendations. The focus of the working group should be on documenting the system level effects to host IP stacks and identification of gaps between the existing IETF recommendations and existing practice. The working group shall address both IPv4 and IPv6 as well as stateless and stateful configuration. Network discovery and selection on lower layers as defined by RFC 5113 is out of scope. Also, the group shall not develop new protocol or policy mechanisms; recommendations and gap analysis from the group are solely based on existing solutions. The group shall not assume any software beyond basic IP protocol support on its peers or in network nodes. No work will be done to enable traffic flows to move from one interface to another. The group recognizes existing work on mechanisms that require peer or network support for moving traffic flows such as RFC 5206, RFC 4980 and the use of multiple care-of addresses in Mobile IPv6. This group does not work on or impact such mechanisms. Once the group has completed its work items, the IETF can make an informed decision about rechartering the working group to define new mechanisms or asking other, specialized working groups (such as DHC or 6MAN) to deal with specific issues. Milestones: May 2009 WG chartered July 2009 Initial draft on problem statement adopted by the WG September 2009 Initial draft on existing practices adopted by the WG Jan 2010 Initial best current practices draft adopted by the WG March 2010 Problem statement draft submitted to the IESG for publication as an Informational RFC July 2010 Existing practices draft submitted to the IESG for publication as an Informational RFC September 2010 Best current practices draft submitted to the IESG for publication as a BCP October 2010 Recharter or close From dromasca@avaya.com Sun Apr 5 08:54: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 BC4DD3A6943; Sun, 5 Apr 2009 08:54:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.508 X-Spam-Level: X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091, 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 w9hwrzTg-cIg; Sun, 5 Apr 2009 08:54:14 -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 A497C3A677D; Sun, 5 Apr 2009 08:54:14 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.39,326,1235970000"; d="scan'208";a="166993029" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 05 Apr 2009 11:55:19 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Apr 2009 11:55:18 -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, 5 Apr 2009 17:54:59 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Internal WG Review: Network-Based Mobility Extensions (NETEXT) Thread-Index: Acm0b7XO21panpLQSTGLQHr/gU2npABlyLMg From: "Romascanu, Dan (Dan)" To: , , Subject: [dns-dir] FW: Internal WG Review: Network-Based Mobility Extensions (NETEXT) 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, 05 Apr 2009 15:54:15 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Friday, April 03, 2009 6:18 PM To: iesg@ietf.org; iab@iab.org Subject: Internal WG Review: Network-Based Mobility Extensions (NETEXT)=20 A new IETF working group is being considered in the Internet Area. The draft charter for this working group is provided below for your review and comment. Review time is one week. The IETF Secretariat Network-Based Mobility Extensions (NETEXT) --------------------------------------------- Last Modified: 2009-04-03 Current Status: Proposed Working Group Chair(s): TBD Internet Area Director(s): Ralph Droms Jari Arkko Internet Area Advisor: TBD Mailing Lists: http://www.mobileip.jp/mailman/listinfo/netext Description of Working Group: Proxy Mobile IPv6, specified in RFC 5213, is a network-based mobility protocol. It uses a Mobile Access Gateway (MAG) and a Local Mobility Anchor (LMA) to allow hosts to move around within a domain while keeping their address or address prefix stable. Proxy Mobile IPv6 has been incorporated into a number of products and deployments are starting. Certain deployment considerations, including localized routing and bulk refresh of lifetime are already emerging. The working group will focus on the following topics relevant for network-based mobility: Localized Routing: a specification for routing traffic between the MAG(s) without involving the LMA. That is, allow the MAGs to route traffic between hosts from one MAG to another, without being tunneled all the way to the LMA. This reduces latency and backhaul load. Applications such as voice can benefit from the reduced latency. Hosts are not affected, as they still send and receive their packets via the MAG. Bulk Refresh: a specification of improving the signaling load for binding lifetime refresh. The current specifications call for the handling of each mobility session independent of each other. When a large number of hosts are served by a single MAG, a periodic refresh of the binding lifetimes can lead to a signaling storm. The purpose of the Bulk Refresh feature is to construct a protocol feature that allows such refreshes to occur on a per-MAG basis. LMA Redirection: a specification for allowing an LMA to redirect a MAG to another LMA. This is primarily needed as a way to perform load balancing, and is complementary to the initial LMA discovery work in the NETLMM WG. The proposed activity will be complementary to the existing IETF Working Groups, notably the NETLMM and MEXT WGs. The NETEXT working group will also act as the primary forum where new extensions on top of the Proxy Mobile IPv6 protocol can be developed. The addition of such new extensions to the working group involves addition of the extension to this charter through the normal rechartering process. Milestones May 2009 WG chartered July 2009 Initial WG draft on Bulk Refresh September 2009 Initial WG draft on LMA Redirection November 2009 Initial WG draft on Route Optimization December 2009 Submit Bulk Refresh to IESG for publication as a Proposed Standard RFC January 2009 Submit LMA Redirection to IESG for publication as a Proposed Standard RFC April 2010 Submit Route Optimization to IESG for publication as a Proposed Standard RFC From ogud@ogud.com Mon Apr 6 07:11: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 3779B3A6935 for ; Mon, 6 Apr 2009 07:11:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.178 X-Spam-Level: X-Spam-Status: No, score=-1.178 tagged_above=-999 required=5 tests=[AWL=-1.179, BAYES_50=0.001] 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 bFG0eJ5B89Gq for ; Mon, 6 Apr 2009 07:11:41 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 6AA933A68AD for ; Mon, 6 Apr 2009 07:11:38 -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 n36ECfip043004 for ; Mon, 6 Apr 2009 10:12:42 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200904061412.n36ECfip043004@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 06 Apr 2009 10:12:34 -0400 To: dns-dir@ietf.org From: Olafur Gudmundsson 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] Anybody else trying to call in ? 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, 06 Apr 2009 14:11:42 -0000 I hear only music, with periodic message that we are waiting for chair person to dial in. Olafur From peter@denic.de Mon Apr 6 09:07: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 48D833A6C1A for ; Mon, 6 Apr 2009 09:07:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.226 X-Spam-Level: X-Spam-Status: No, score=-6.226 tagged_above=-999 required=5 tests=[AWL=0.023, 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 zF8VtoxrwgPd for ; Mon, 6 Apr 2009 09:07:29 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 946413A6CBD for ; Mon, 6 Apr 2009 09:07:28 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1LqrN9-00041v-Ns; Mon, 06 Apr 2009 18:08:31 +0200 Received: from localhost by x27.adm.denic.de with local id 1LqrK1-0008FC-TD; Mon, 06 Apr 2009 18:05:17 +0200 Date: Mon, 6 Apr 2009 18:05:17 +0200 From: Peter Koch To: Olafur Gudmundsson Message-ID: <20090406160517.GB30703@x27.adm.denic.de> References: <200904061412.n36ECfip043004@stora.ogud.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200904061412.n36ECfip043004@stora.ogud.com> User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Anybody else trying to call in ? 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, 06 Apr 2009 16:07:30 -0000 On Mon, Apr 06, 2009 at 10:12:34AM -0400, Olafur Gudmundsson wrote: > > I hear only music, with periodic message that we are waiting for chair > person to dial in. since this was short after the San Francisco IETF, I had suggested to skip this call and move the next one from early May (collision with the RIPE meeting) to 2008-04-27 1400 UTC. Apologies if my badly chosen subject line confused you. Regards, Peter From ogud@ogud.com Thu Apr 9 11:28:55 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 03FAF3A6C0A for ; Thu, 9 Apr 2009 11:28:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.451 X-Spam-Level: X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[AWL=0.148, 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 I2TIz9ZPgzMm for ; Thu, 9 Apr 2009 11:28:54 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id 1B50F3A6C03 for ; Thu, 9 Apr 2009 11:28:53 -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 n39IU0K8091298 for ; Thu, 9 Apr 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Thu, 9 Apr 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: <20090409_183001_016092.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-faltstrom-root-trust-anchor-validation-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: Thu, 09 Apr 2009 18:28:55 -0000 Count: 15 Network Working Group P. Faltstrom Internet-Draft Cisco Intended status: Informational J. Schlyter Expires: October 10, 2009 Kirei AB April 8, 2009 Validation of the root trust anchor for the DNS draft-faltstrom-root-trust-anchor-validation-00 Abstract This document describes practical requirements and needs for automatic validation of the root trust anchor for the DNS. It also proposes a mechanism using PGP and/or S/MIME that can be used to fulfil the requirements. From ogud@ogud.com Thu Apr 9 11:31: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 25D243A6CC1 for ; Thu, 9 Apr 2009 11:31:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.454 X-Spam-Level: X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145, 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 h0fiecFcasUW for ; Thu, 9 Apr 2009 11:31:58 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id A22D628B23E for ; Thu, 9 Apr 2009 11:31:28 -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 n39IU1kX091335 for ; Thu, 9 Apr 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Thu, 9 Apr 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: <20090409_183001_005206.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-dolmatov-dnsext-dnssec-gost-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: Thu, 09 Apr 2009 18:31:59 -0000 Count: 33 DNS Extensions working group V.Dolmatov, Ed. Internet-Draft Cryptocom Ltd. Intended status: Standards Track April 8, 2009 Expires: December 31, 2009 Use of GOST signature algorithms in DNSKEY and RRSIG Resource Records for DNSSEC draft-dolmatov-dnsext-dnssec-gost-00 Abstract This document describes how to produce GOST signature and hash algorithms DNSKEY and RRSIG resource records for use in the Domain Name System Security Extensions (DNSSEC, RFC 4033, RFC 4034, and RFC 4035). From ogud@ogud.com Fri Apr 10 07:18:35 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 AE6623A69CD for ; Fri, 10 Apr 2009 07:18:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.457 X-Spam-Level: X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 hGHofH5zH-FL for ; Fri, 10 Apr 2009 07:18:35 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id BFF4F3A6D87 for ; Fri, 10 Apr 2009 07:18:34 -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 n3AEJfTQ000592 for ; Fri, 10 Apr 2009 10:19:42 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200904101419.n3AEJfTQ000592@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 10 Apr 2009 10:17:24 -0400 To: dns-dir@ietf.org From: Olafur Gudmundsson In-Reply-To: <20090409_183001_005206.ogud@ogud.com> References: <20090409_183001_005206.ogud@ogud.com> 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] DNS Early Warn: draft-dolmatov-dnsext-dnssec-gost-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, 10 Apr 2009 14:18:35 -0000 This is an "interesting" document that is asking DNSEXT to adopt it. Right now I can not find a full description of the algorithms specified, a ecliptic curve a hash algorithm Does anyone on DNS-dir know, any more about these algorithms to give me (and Andrew) background on these to lead intelligent discussion on this proposal. Olafur At 14:30 09/04/2009, Olafur_DNS_EARLY_WARNING wrote: >Count: 33 DNS Extensions working >group V.Dolmatov, Ed. >Internet-Draft Cryptocom Ltd. >Intended status: Standards Track April 8, 2009 >Expires: December 31, 2009 > > > Use of GOST signature algorithms in DNSKEY and RRSIG Resource Records > for DNSSEC > draft-dolmatov-dnsext-dnssec-gost-00 > > Abstract > This document describes how to produce GOST signature and hash algorithms > DNSKEY and RRSIG resource records for use in the Domain Name System > Security Extensions (DNSSEC, RFC 4033, RFC 4034, and RFC 4035). > > >_______________________________________________ >dns-dir mailing list >dns-dir@ietf.org >https://www.ietf.org/mailman/listinfo/dns-dir From roy@dnss.ec Fri Apr 10 08:16:36 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 B20653A6DED for ; Fri, 10 Apr 2009 08:16:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.149 X-Spam-Level: X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.100, 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 rgFhoyYHMF1y for ; Fri, 10 Apr 2009 08:16:35 -0700 (PDT) Received: from mail.schlyter.se (trinitario.schlyter.se [195.47.254.10]) by core3.amsl.com (Postfix) with ESMTP id C77A23A6EE5 for ; Fri, 10 Apr 2009 08:15:57 -0700 (PDT) Received: from a82-94-105-56.adsl.xs4all.nl (a82-94-105-56.adsl.xs4all.nl [82.94.105.56]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: roy) by mail.schlyter.se (Postfix) with ESMTPSA id 93FBE2DCBA; Fri, 10 Apr 2009 17:17:03 +0200 (MEST) From: Roy Arends To: Olafur Gudmundsson In-Reply-To: <200904101419.n3AEJfTQ000592@stora.ogud.com> References: <20090409_183001_005206.ogud@ogud.com> <200904101419.n3AEJfTQ000592@stora.ogud.com> Message-Id: <50848061-A5F8-429A-9CC5-5181893FE004@dnss.ec> 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, 10 Apr 2009 17:16:59 +0200 X-Mailer: Apple Mail (2.930.3) Cc: dns-dir@ietf.org Subject: Re: [dns-dir] DNS Early Warn: draft-dolmatov-dnsext-dnssec-gost-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, 10 Apr 2009 15:16:36 -0000 On Apr 10, 2009, at 4:17 PM, Olafur Gudmundsson wrote: > This is an "interesting" document that is asking DNSEXT to adopt it. > Right now I can not find a full description of the algorithms > specified, > a ecliptic curve > a hash algorithm > > Does anyone on DNS-dir know, any more about these algorithms to give > me (and Andrew) > background on these to lead intelligent discussion on this proposal. I understand there is literature about the cryptanalysis of GOST-R 34.10-2001 and 34.11-94 (see mendel et al [1]). I am no expert in this realm, but I do want to point out that we've 'updated' DNSSEC to avoid the use of hash algorithms that needs less rounds than brute-force to produce a pre-image (MD5, SHA1) or a collision. I think we need to leave this one for the security directorate. I am not comfortable to have the DNS-DIR advice the AD's [for|against] adoption without a clear reference. What I also would be interested in, but that is a lower priority for me, is a technical reason why RSA-SHA256 does not suffice. I understand there are political reasons against using RSA-SHAX. If we allow ourself to work with arguments outside our techno-policy mandate, we have a wholelotta work waiting for us. As said, not for or against adoption, but maybe just not our call. Kind regards, Roy. [1] http://wiki.uni.lu/esc/docs/mendel_gost.pdf (also see: http://www.google.com/search?q=GOST+R+34.11-94+cryptanalysis http://www.google.com/search?q=GOST+R+34.10-2001+cryptanalysis ) From dromasca@avaya.com Fri Apr 17 00:34:20 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 47BFB3A6A4C; Fri, 17 Apr 2009 00:34:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.52 X-Spam-Level: X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079, 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 X5M7zI-rRqmx; Fri, 17 Apr 2009 00:34:19 -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 03F5C3A6A26; Fri, 17 Apr 2009 00:34:18 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,203,1238990400"; d="scan'208";a="168185022" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 17 Apr 2009 03:35:31 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Apr 2009 03:35:31 -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, 17 Apr 2009 09:35:15 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for April 23, 2009 Telechat Thread-index: Acm+22A4Hv2nJ1qcToGAcYR2BmAbgQAUljkg From: "Romascanu, Dan (Dan)" To: , , "MIB Doctors (E-mail)" , Subject: [dns-dir] FW: PRELIMINARY Agenda and Package for April 23, 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, 17 Apr 2009 07:34:20 -0000 Please find below the preliminary agenda of the 4/23 telechat. Please read and review the relevant documents, as well as the charters of the WGs that are being brought for approval by the IESG. Comments, concerns and questions should be sent before 4/22 COB.=20 Thanks and Regards, Dan =20 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 10=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-radext-design-07.txt RADIUS Design Guidelines (BCP) - 2 of 10=20 Token: Dan Romascanu o draft-ietf-ipfix-exporting-type-03.txt Exporting Type Information for IPFIX Information Elements (Proposed=20 Standard) - 3 of 10=20 Token: Dan Romascanu o draft-ietf-ipfix-file-03.txt Specification of the IPFIX File Format (Proposed Standard) - 4 of 10 Token: Dan Romascanu o draft-ietf-dime-mip6-split-16.txt Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction=20 (Proposed Standard) - 5 of 10=20 Token: Dan Romascanu o draft-ietf-netlmm-grekey-option-06.txt GRE Key Option for Proxy Mobile IPv6 (Proposed Standard) - 6 of 10=20 Token: Jari Arkko o draft-ietf-dhc-container-opt-05.txt Container Option for Server Configuration (Proposed Standard) - 7 of 10=20 Token: Jari Arkko o draft-ietf-pkix-3281update-04.txt An Internet Attribute Certificate Profile for Authorization (Proposed Standard) - 8 of 10=20 Token: Tim Polk o draft-ietf-dccp-serv-codes-08.txt The DCCP Service Code (Proposed Standard) - 9 of 10=20 Token: Lars Eggert o rfc3852.txt Cryptographic Message Syntax (CMS) (Draft Standard) - 10 of 10=20 Token: Tim Polk 2.1.2 Returning Item o draft-ietf-geopriv-radius-lo-23.txt Carrying Location Objects in RADIUS and Diameter (Proposed Standard) - 1 of=20 1=20 Note: Did new LC because previous one did not mention DOWNREF.=20 Token: Cullen Jennings 2.2 Individual Submissions 2.2.1 New Item o draft-atlas-icmp-unnumbered-06.txt Extending ICMP for Interface and Next-hop Identification (Proposed=20 Standard) - 1 of 1=20 Token: Jari Arkko 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 3=20 Token: Lars Eggert o draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt OSPFv2 Routing Protocols Extensions for ASON Routing (Experimental) - 2 of=20 3=20 Token: Adrian Farrel o draft-ietf-pana-statemachine-10.txt State Machines for Protocol for Carrying Authentication for Network Access=20 (PANA) (Informational) - 3 of 3=20 Token: Jari Arkko 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 o draft-lochter-pkix-brainpool-ecc-03.txt ECC Brainpool Standard Curves and Curve Generation (Informational) - 1 of 2=20 Note: waiting for confirmation that no IPR disclosure is needed.=20 Token: Tim Polk o draft-bberry-rfc4938bis-00.txt PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 2 of 2=20 Token: Jari Arkko 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Open Web authentication (oauth) - 1 of 1 Token: Lisa Dusseault 4.1.2 Proposed for Approval o Multiple Interfaces (mif) - 1 of 3 Token: Jari Arkko o Locator/ID Separation Protocol (lisp) - 2 of 3 Token: Jari Arkko o Network-Based Mobility Extensions (netext) - 3 of 3 Token: Jari Arkko 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 Apr 17 06:47: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 661B43A6941 for ; Fri, 17 Apr 2009 06:47:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.392 X-Spam-Level: X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=0.207, 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 9P5TBJYu6HDt for ; Fri, 17 Apr 2009 06:47:41 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id EF0053A6837 for ; Fri, 17 Apr 2009 06:47:40 -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 n3HDmpYP073659; Fri, 17 Apr 2009 09:48:51 -0400 (EDT) (envelope-from ogud@ogud.com) Message-Id: <200904171348.n3HDmpYP073659@stora.ogud.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 17 Apr 2009 09:46:59 -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 April 23, 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, 17 Apr 2009 13:47:42 -0000 None of the documents are in the DNS early warning data base. Olafur At 03:35 17/04/2009, Romascanu, Dan (Dan) wrote: >Please find below the preliminary agenda of the 4/23 telechat. Please >read and review the relevant documents, as well as the charters of the >WGs that are being brought for approval by the IESG. Comments, concerns >and questions should be sent before 4/22 COB. > >Thanks and Regards, > >Dan > > >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 10 > Note: IESG: Please read the Document Shepherd Writeup, we need to >discuss > the "Updates: 793" issue. > Token: Lars Eggert > o draft-ietf-radext-design-07.txt > RADIUS Design Guidelines (BCP) - 2 of 10 > Token: Dan Romascanu > o draft-ietf-ipfix-exporting-type-03.txt > Exporting Type Information for IPFIX Information Elements (Proposed > Standard) - 3 of 10 > Token: Dan Romascanu > o draft-ietf-ipfix-file-03.txt > Specification of the IPFIX File Format (Proposed Standard) - 4 of 10 > > Token: Dan Romascanu > o draft-ietf-dime-mip6-split-16.txt > Diameter Mobile IPv6: Support for Home Agent to Diameter Server >Interaction > (Proposed Standard) - 5 of 10 > Token: Dan Romascanu > o draft-ietf-netlmm-grekey-option-06.txt > GRE Key Option for Proxy Mobile IPv6 (Proposed Standard) - 6 of 10 > Token: Jari Arkko > o draft-ietf-dhc-container-opt-05.txt > Container Option for Server Configuration (Proposed Standard) - 7 of >10 > Token: Jari Arkko > o draft-ietf-pkix-3281update-04.txt > An Internet Attribute Certificate Profile for Authorization >(Proposed > > Standard) - 8 of 10 > Token: Tim Polk > o draft-ietf-dccp-serv-codes-08.txt > The DCCP Service Code (Proposed Standard) - 9 of 10 > Token: Lars Eggert > o rfc3852.txt > Cryptographic Message Syntax (CMS) (Draft Standard) - 10 of 10 > Token: Tim Polk > >2.1.2 Returning Item > o draft-ietf-geopriv-radius-lo-23.txt > Carrying Location Objects in RADIUS and Diameter (Proposed Standard) >- >1 of > 1 > Note: Did new LC because previous one did not mention DOWNREF. > Token: Cullen Jennings > > >2.2 Individual Submissions >2.2.1 New Item > o draft-atlas-icmp-unnumbered-06.txt > Extending ICMP for Interface and Next-hop Identification (Proposed > Standard) - 1 of 1 > Token: Jari Arkko > >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 3 > Token: Lars Eggert > o draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt > OSPFv2 Routing Protocols Extensions for ASON Routing (Experimental) >- >2 of > 3 > Token: Adrian Farrel > o draft-ietf-pana-statemachine-10.txt > State Machines for Protocol for Carrying Authentication for Network >Access > (PANA) (Informational) - 3 of 3 > Token: Jari Arkko > >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 > o draft-lochter-pkix-brainpool-ecc-03.txt > ECC Brainpool Standard Curves and Curve Generation (Informational) - >1 >of 2 > Note: waiting for confirmation that no IPR disclosure is needed. > Token: Tim Polk > o draft-bberry-rfc4938bis-00.txt > PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link >Metrics > > (Informational) - 2 of 2 > Token: Jari Arkko > > >4. Working Group Actions >4.1 WG Creation >4.1.1 Proposed for IETF Review > o Open Web authentication (oauth) - 1 of 1 > Token: Lisa Dusseault >4.1.2 Proposed for Approval > o Multiple Interfaces (mif) - 1 of 3 > Token: Jari Arkko > o Locator/ID Separation Protocol (lisp) - 2 of 3 > Token: Jari Arkko > o Network-Based Mobility Extensions (netext) - 3 of 3 > Token: Jari Arkko >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 dromasca@avaya.com Mon Apr 20 04:42: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 7A5113A6AE3 for ; Mon, 20 Apr 2009 04:42:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.514 X-Spam-Level: X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 rrr9fOFsa4yq for ; Mon, 20 Apr 2009 04:42:31 -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 A49C03A6ACD for ; Mon, 20 Apr 2009 04:42:31 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,217,1238990400"; d="scan'208,217";a="158893050" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 20 Apr 2009 07:43:46 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Apr 2009 07:43:46 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9C1AD.3FF015D1" Date: Mon, 20 Apr 2009 13:43:37 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: test Thread-Index: AcnBrT5/RwspZUjlSDal3CSWzMBCvA== From: "Romascanu, Dan (Dan)" To: Subject: [dns-dir] test 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, 20 Apr 2009 11:42:32 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9C1AD.3FF015D1 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please disregard this.=20 =20 Dan =20 ------_=_NextPart_001_01C9C1AD.3FF015D1 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Please = disregard=20 this.
 
Dan
 
------_=_NextPart_001_01C9C1AD.3FF015D1-- From jari.arkko@piuha.net Mon Apr 20 04:43: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 AAA4E3A6AE3 for ; Mon, 20 Apr 2009 04:43:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.548 X-Spam-Level: X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051, 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 T+XNdKLTUXRU for ; Mon, 20 Apr 2009 04:43:44 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id EA7BB3A6ACD for ; Mon, 20 Apr 2009 04:43:43 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 3022919878B for ; Mon, 20 Apr 2009 14:44:59 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id EB1EC198665 for ; Mon, 20 Apr 2009 14:44:58 +0300 (EEST) Message-ID: <49EC602E.9040002@piuha.net> Date: Mon, 20 Apr 2009 14:44:46 +0300 From: Jari Arkko User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: dns-dir@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [dns-dir] test 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, 20 Apr 2009 11:43:44 -0000 Does this work? Jari Romascanu, Dan (Dan) wrote: > Please disregard this. > > Dan > > ------------------------------------------------------------------------ > > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir > From jari.arkko@piuha.net Mon Apr 20 04:46:11 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 AC10F3A68E7 for ; Mon, 20 Apr 2009 04:46:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 jzVYSjhwNDuo for ; Mon, 20 Apr 2009 04:46:10 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 3B9E528C2C3 for ; Mon, 20 Apr 2009 04:45:44 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 6CF9D19878B; Mon, 20 Apr 2009 14:46:59 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 2969D198665; Mon, 20 Apr 2009 14:46:58 +0300 (EEST) Message-ID: <49EC60A7.2000208@piuha.net> Date: Mon, 20 Apr 2009 14:46:47 +0300 From: Jari Arkko User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: dns directorate Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: "Bajko Gabor \(Nokia-NET/SanDiego\)" , "Devarapalli, Vijay" Subject: [dns-dir] help with NAPTR & S-NAPTR issues 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, 20 Apr 2009 11:46:11 -0000 (Sorry for duplicates; this e-mail got lost when I sent it to the wrong dns-dir address.) Directorate, I have a document in AD review (draft-ietf-mipshop-mos-dns-discovery) where I had a number of question marks relating to the use and registration of NATPTRs. I also asked Leslie Daigle for some help and she suggested S-NAPTR might have been a more appropriate tool for this task. The problem is, she is busy and I'm clueless about NAPTR. I'd like to find one volunteer with such clue from the directorate, and put the volunteer, me, and the author and chair (Cced) to the same conference call sometime this or next week. The volunteer should help us understand whether something needs to change in the document, and if so, what. Jari Some links: http://tools.ietf.org/html/draft-ietf-mipshop-mos-dns-discovery-04 http://www.ietf.org/mail-archive/web/mipshop/current/msg04183.html From peter@denic.de Mon Apr 20 05:10:08 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 E63043A6C13 for ; Mon, 20 Apr 2009 05:10:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.019 X-Spam-Level: X-Spam-Status: No, score=-6.019 tagged_above=-999 required=5 tests=[AWL=0.230, 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 FvHsXj2vGWX5 for ; Mon, 20 Apr 2009 05:10:08 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 0A9C23A6ADA for ; Mon, 20 Apr 2009 05:10:07 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1LvsLI-0002WZ-Pp; Mon, 20 Apr 2009 14:11:20 +0200 Received: from localhost by x27.adm.denic.de with local id 1LvsI4-0006Ev-9E; Mon, 20 Apr 2009 14:08:00 +0200 Date: Mon, 20 Apr 2009 14:08:00 +0200 From: Peter Koch To: Jari Arkko Message-ID: <20090420120800.GJ12052@x27.adm.denic.de> References: <49EC60A7.2000208@piuha.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49EC60A7.2000208@piuha.net> User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: "Bajko Gabor \(Nokia-NET/SanDiego\)" , "Devarapalli, Vijay" , dns directorate Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 20 Apr 2009 12:10:09 -0000 Jari, > I have a document in AD review (draft-ietf-mipshop-mos-dns-discovery) > where I had a number of question marks relating to the use and > registration of NATPTRs. I also asked Leslie Daigle for some help and > she suggested S-NAPTR might have been a more appropriate tool for this > task. The problem is, she is busy and I'm clueless about NAPTR. I'd like > to find one volunteer with such clue from the directorate, and put the > volunteer, me, and the author and chair (Cced) to the same conference > call sometime this or next week. The volunteer should help us understand > whether something needs to change in the document, and if so, what. I vaguely remembered I had reviewed this draft in an earlier version. NAPTR RRs are defined in the DDDS context only and for less structured or specialized name spaces ther are S-NAPTR and U-NAPTR. I am not a particular fan of either one because I don't believe in DNS as a service discovery (rather than a service location) mechanism. The crucial point in the draft is: The procedures defined here assume that the MN knows the domain name of the network where it wants to locate a Mobility Server. The domain name of the network can either be pre-configured, discovered This assumes that "a network" has "a domain name", which I disagree with. Apart from that IO'd be willing to help, of course. If any of you is going to be at the RIPE meeting early May, that would even allow a face 2 face discussion. -Peter From pfaltstr@cisco.com Mon Apr 20 05:31: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 15FCA3A68AC for ; Mon, 20 Apr 2009 05:31:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.68 X-Spam-Level: X-Spam-Status: No, score=-8.68 tagged_above=-999 required=5 tests=[AWL=1.619, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8] 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 voQ6nZ41QrSo for ; Mon, 20 Apr 2009 05:31:11 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 6297B3A6E2C for ; Mon, 20 Apr 2009 05:30:51 -0700 (PDT) X-Files: PGP.sig : 186 X-IronPort-AV: E=Sophos;i="4.40,217,1238976000"; d="sig'?scan'208";a="38677496" Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 20 Apr 2009 12:32:06 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n3KCW6du011785; Mon, 20 Apr 2009 14:32:06 +0200 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3KCW6Rw016539; Mon, 20 Apr 2009 12:32:06 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Apr 2009 14:32:06 +0200 Received: from host-217-213-51-151.homerun.telia.com ([10.61.95.66]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Apr 2009 14:32:02 +0200 Message-Id: <4CC3C17D-C467-4107-8B99-3CBA37E550A7@cisco.com> From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: Peter Koch In-Reply-To: <20090420120800.GJ12052@x27.adm.denic.de> Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-683--69498192" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 20 Apr 2009 14:31:46 +0200 References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 20 Apr 2009 12:32:02.0301 (UTC) FILETIME=[01AABAD0:01C9C1B4] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3261; t=1240230726; x=1241094726; c=relaxed/simple; s=amsdkim1002; 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]=20help=20with=20NAPTR=20&=20S -NAPTR=20issues |Sender:=20; bh=nCJX1qG+skuP9SZcB+HlgtvRoS9vRUfkKafGgUXGpS8=; b=wN6RG9Rmf7lVl3NN9mzlriEm4fjFwaV50FiTqD7Qc3JFW/rvD+1bFKTTle b3oqUPk2u4imHTYTeibKy/8Etw2uYr2WVEqP0HAwj9pC7qF70JjmICLd+bBN JURJg1x3qy; Authentication-Results: ams-dkim-1; header.From=paf@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); Cc: "Bajko Gabor \(Nokia-NET/SanDiego\)" , "Devarapalli, Vijay" , dns directorate Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 20 Apr 2009 12:31:13 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-683--69498192 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On 20 apr 2009, at 14.08, Peter Koch wrote: >> I have a document in AD review (draft-ietf-mipshop-mos-dns-discovery) >> where I had a number of question marks relating to the use and >> registration of NATPTRs. I also asked Leslie Daigle for some help and >> she suggested S-NAPTR might have been a more appropriate tool for >> this >> task. The problem is, she is busy and I'm clueless about NAPTR. I'd >> like >> to find one volunteer with such clue from the directorate, and put >> the >> volunteer, me, and the author and chair (Cced) to the same conference >> call sometime this or next week. The volunteer should help us >> understand >> whether something needs to change in the document, and if so, what. > > I vaguely remembered I had reviewed this draft in an earlier version. > NAPTR RRs are defined in the DDDS context only and for less structured > or specialized name spaces ther are S-NAPTR and U-NAPTR. I am not a > particular > fan of either one because I don't believe in DNS as a service > discovery > (rather than a service location) mechanism. > > The crucial point in the draft is: > > The procedures defined here assume that the MN knows the domain name > of the network where it wants to locate a Mobility Server. The > domain name of the network can either be pre-configured, discovered > > This assumes that "a network" has "a domain name", which I disagree > with. > Apart from that IO'd be willing to help, of course. If any of you is > going to be at the RIPE meeting early May, that would even allow a > face 2 face discussion. This is the key thing. And also something Stuart Cheshire has asked about. For example why not what today is "search domain" (in for example DHCP, and resolver configuration) is this "home domain". Regarding the proposal, well, it could be ok but sounds a bit too complicated I think. I have two questions: - I am nervous the terms IS, ES and CS, are too short. I do see future collisions regarding naming (in the prefix in the DNS). - Is it really the case that you want to look for what services exists for a certain domain? If you follow the bonjour way of doing things you should instead look up: _mobility_services._tcp.home.domain. IN PTR _es._tcp.home.domain. _mobility_services._tcp.home.domain. IN PTR _cs._tcp.home.domain. Etc...and then the SRV etc. So, there is an architectural choice whether you want to go the (S-)NAPTR path, or bonjour/zeroconf path. Patrik - Why do they not "just" do the bonjour version of the lookup, i.e. look up --Apple-Mail-683--69498192 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) iD8DBQFJ7GsyvHlR2X0luNwRAhArAJ9PnRL1xnHg1mUzTD/D3vb31sjZdgCgzo+0 mvZrqZrWrfS3QJlh3BW07FM= =kGPX -----END PGP SIGNATURE----- --Apple-Mail-683--69498192-- From Gabor.Bajko@nokia.com Tue Apr 21 15:56:36 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 0173A3A68BD for ; Tue, 21 Apr 2009 15:56:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 GnrTGaNUeEui for ; Tue, 21 Apr 2009 15:56:35 -0700 (PDT) Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id ACAC43A67F7 for ; Tue, 21 Apr 2009 15:56:34 -0700 (PDT) Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n3LMvSFW026065; Wed, 22 Apr 2009 01:57:40 +0300 Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Apr 2009 01:57:29 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Apr 2009 01:57:24 +0300 Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Wed, 22 Apr 2009 00:57:24 +0200 From: To: , Date: Wed, 22 Apr 2009 00:57:21 +0200 Thread-Topic: [dns-dir] help with NAPTR & S-NAPTR issues Thread-Index: AcnBsTLd+6MMvbttSFCJGCH1p7IwWABHIC6Q Message-ID: References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> In-Reply-To: <20090420120800.GJ12052@x27.adm.denic.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 21 Apr 2009 22:57:24.0677 (UTC) FILETIME=[8928AF50:01C9C2D4] X-Nokia-AV: Clean X-Mailman-Approved-At: Wed, 22 Apr 2009 08:11:17 -0700 Cc: vijay@wichorus.com, dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 21 Apr 2009 22:56:36 -0000 Hi Peter, Patrik >The crucial point in the draft is: > > The procedures defined here assume that the MN knows the=20 >domain name=20 > of the network where it wants to locate a Mobility Server. The=20 > domain name of the network can either be pre-configured,=20 >discovered=20 > >This assumes that "a network" has "a domain name", which I=20 >disagree with. Would the below re-write of the paragraph you cite above solve the problem? The procedures defined in this document assume that the MN knows the search= domain (DNS suffix) where it wants to locate a Mobility Server.=20 When the MN wants to find Mobility Servers in its current visited network, = it can use DHCP option 15 to request the domain name it should use when res= olving hostnames via DNS. The domain name suffix returned in the option can= be used as the search domain. When the MN wants to find Mobility Servers in the home network, it can use = the home domain of its subscription as the search domain. If the MN wants to find Mobility Servers in a 3rd party operated network (w= hich is not its current visited, or its home network) it needs to have the = search domains of those 3rd party operated networks preconfigured, or use I= EEE 802.21 Information Service query [IEEE802.21] to find the home domains = of the networks operating in the location of interest. The naming issues mentioned by Patrik in the other mail can easily be addre= ssed. Using the Bonjour way in my opinion wouldn't solve the issue as it has the = same problem, ie how to find the suffix of the search domain. Thanks, - gabor >-----Original Message----- >From: Peter Koch [mailto:peter@denic.de] On Behalf Of ext Peter Koch >Sent: Monday, April 20, 2009 5:08 AM >To: Jari Arkko >Cc: dns directorate; Bajko Gabor (Nokia);=20 >Devarapalli, Vijay >Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues > >Jari, > >> I have a document in AD review=20 >(draft-ietf-mipshop-mos-dns-discovery) >> where I had a number of question marks relating to the use and=20 >> registration of NATPTRs. I also asked Leslie Daigle for=20 >some help and=20 >> she suggested S-NAPTR might have been a more appropriate=20 >tool for this=20 >> task. The problem is, she is busy and I'm clueless about=20 >NAPTR. I'd=20 >> like to find one volunteer with such clue from the=20 >directorate, and=20 >> put the volunteer, me, and the author and chair (Cced) to the same=20 >> conference call sometime this or next week. The volunteer=20 >should help=20 >> us understand whether something needs to change in the=20 >document, and if so, what. > >I vaguely remembered I had reviewed this draft in an earlier version. >NAPTR RRs are defined in the DDDS context only and for less=20 >structured or specialized name spaces ther are S-NAPTR and=20 >U-NAPTR. I am not a particular fan of either one because I=20 >don't believe in DNS as a service discovery (rather than a=20 >service location) mechanism. > >The crucial point in the draft is: > > The procedures defined here assume that the MN knows the=20 >domain name=20 > of the network where it wants to locate a Mobility Server. The=20 > domain name of the network can either be pre-configured,=20 >discovered=20 > >This assumes that "a network" has "a domain name", which I=20 >disagree with. >Apart from that IO'd be willing to help, of course. If any=20 >of you is going to be at the RIPE meeting early May, that=20 >would even allow a face 2 face discussion. > >-Peter >= From pfaltstr@cisco.com Thu Apr 23 00:08:25 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 B1E843A68C8 for ; Thu, 23 Apr 2009 00:08:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.404 X-Spam-Level: X-Spam-Status: No, score=-7.404 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067] 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 FGRILCUpF9HU for ; Thu, 23 Apr 2009 00:08:24 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id EBC933A6F8A for ; Thu, 23 Apr 2009 00:08:23 -0700 (PDT) X-Files: PGP.sig : 186 X-IronPort-AV: E=Sophos;i="4.40,235,1238976000"; d="sig'?scan'208";a="38943869" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 23 Apr 2009 07:09:40 +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 n3N79eVk002741; Thu, 23 Apr 2009 09:09:40 +0200 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3N79e8I006739; Thu, 23 Apr 2009 07:09:40 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Apr 2009 09:09:39 +0200 Received: from 95.209.77.252.bredband.tre.se ([10.61.81.200]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Apr 2009 09:09:36 +0200 Message-Id: <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: In-Reply-To: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-82-170366641" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 23 Apr 2009 09:09:31 +0200 References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 23 Apr 2009 07:09:37.0160 (UTC) FILETIME=[764DB880:01C9C3E2] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4918; t=1240470580; x=1241334580; 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]=20help=20with=20NAPTR=20&=20S -NAPTR=20issues |Sender:=20; bh=yxGydyf4UgZqU2fcp5ZAeBTeZwuImi0QSJBLuZTbBwM=; b=eX0SF0hOCxp+jk5bq6pqcKN4Ue3+PDAJ9YWoVlutYIBxOkyXToOt4cwIQC UwRiaTgBEKGn5SB1mLLwR9QHsHKbqx2yNgfXA3YBpXSbybMEiqLzLz3dVZ9o zEAzgcUzV0; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: pk@denic.de, vijay@wichorus.com, dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 23 Apr 2009 07:08:25 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-82-170366641 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On 22 apr 2009, at 00.57, wrote: > Hi Peter, Patrik > >> The crucial point in the draft is: >> >> The procedures defined here assume that the MN knows the >> domain name >> of the network where it wants to locate a Mobility Server. The >> domain name of the network can either be pre-configured, >> discovered >> >> This assumes that "a network" has "a domain name", which I >> disagree with. > > Would the below re-write of the paragraph you cite above solve the > problem? > > The procedures defined in this document assume that the MN knows the > search domain (DNS suffix) where it wants to locate a Mobility Server. I think we have two problems here. a) Is it correct to use the search domain for usage like this (in a DDDS context) and Bonjour b) Do you want to use DDDS or Bonjour algorithm I think personally the answers are: a: Yes - but we need a generic document that updates the DNS spec that talk about this change b: You want bonjour, as what you do is a more zeroconf algorithm Other people cc:ed might have different opinion. Patrik > When the MN wants to find Mobility Servers in its current visited > network, it can use DHCP option 15 to request the domain name it > should use when resolving hostnames via DNS. The domain name suffix > returned in the option can be used as the search domain. > When the MN wants to find Mobility Servers in the home network, it > can use the home domain of its subscription as the search domain. > If the MN wants to find Mobility Servers in a 3rd party operated > network (which is not its current visited, or its home network) it > needs to have the search domains of those 3rd party operated > networks preconfigured, or use IEEE 802.21 Information Service query > [IEEE802.21] to find the home domains of the networks operating in > the location of interest. > > The naming issues mentioned by Patrik in the other mail can easily > be addressed. > > Using the Bonjour way in my opinion wouldn't solve the issue as it > has the same problem, ie how to find the suffix of the search domain. > > Thanks, > - gabor > > >> -----Original Message----- >> From: Peter Koch [mailto:peter@denic.de] On Behalf Of ext Peter Koch >> Sent: Monday, April 20, 2009 5:08 AM >> To: Jari Arkko >> Cc: dns directorate; Bajko Gabor (Nokia); >> Devarapalli, Vijay >> Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues >> >> Jari, >> >>> I have a document in AD review >> (draft-ietf-mipshop-mos-dns-discovery) >>> where I had a number of question marks relating to the use and >>> registration of NATPTRs. I also asked Leslie Daigle for >> some help and >>> she suggested S-NAPTR might have been a more appropriate >> tool for this >>> task. The problem is, she is busy and I'm clueless about >> NAPTR. I'd >>> like to find one volunteer with such clue from the >> directorate, and >>> put the volunteer, me, and the author and chair (Cced) to the same >>> conference call sometime this or next week. The volunteer >> should help >>> us understand whether something needs to change in the >> document, and if so, what. >> >> I vaguely remembered I had reviewed this draft in an earlier version. >> NAPTR RRs are defined in the DDDS context only and for less >> structured or specialized name spaces ther are S-NAPTR and >> U-NAPTR. I am not a particular fan of either one because I >> don't believe in DNS as a service discovery (rather than a >> service location) mechanism. >> >> The crucial point in the draft is: >> >> The procedures defined here assume that the MN knows the >> domain name >> of the network where it wants to locate a Mobility Server. The >> domain name of the network can either be pre-configured, >> discovered >> >> This assumes that "a network" has "a domain name", which I >> disagree with. >> Apart from that IO'd be willing to help, of course. If any >> of you is going to be at the RIPE meeting early May, that >> would even allow a face 2 face discussion. >> >> -Peter >> > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir --Apple-Mail-82-170366641 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) iD8DBQFJ8BQrvHlR2X0luNwRAhO4AJ9BTh4GrO8Y8MYjf6SbFOkEhUOOWACg9V2h afoi6nOBwsszMXmqL/RYfVI= =1V8I -----END PGP SIGNATURE----- --Apple-Mail-82-170366641-- From pfaltstr@cisco.com Thu Apr 23 22:24:36 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 3CB573A6D76 for ; Thu, 23 Apr 2009 22:24:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.446 X-Spam-Level: X-Spam-Status: No, score=-6.446 tagged_above=-999 required=5 tests=[AWL=-0.747, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 e5DGQrd4AYGr for ; Thu, 23 Apr 2009 22:24:34 -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 DB8C13A6AFB for ; Thu, 23 Apr 2009 22:24:34 -0700 (PDT) X-Files: PGP.sig : 186 X-IronPort-AV: E=Sophos;i="4.40,239,1238976000"; d="sig'?scan'208";a="156363214" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by sj-iport-3.cisco.com with ESMTP; 24 Apr 2009 05:25:47 +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 n3O5PlMs003750; Fri, 24 Apr 2009 07:25:47 +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 n3O5Pl5v006938; Fri, 24 Apr 2009 05:25:47 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Apr 2009 07:25:46 +0200 Received: from [172.27.30.87] ([10.61.84.45]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Apr 2009 07:25:46 +0200 Message-Id: From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: In-Reply-To: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-175-250540280" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 24 Apr 2009 07:25:45 +0200 References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 24 Apr 2009 05:25:46.0288 (UTC) FILETIME=[1ED3DB00:01C9C49D] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6604; t=1240550747; x=1241414747; 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]=20help=20with=20NAPTR=20&=20S -NAPTR=20issues |Sender:=20; bh=M6zsYJHZAZJPDfwAYuLiHPnVxiI6zi12BJpbEGFHIqk=; b=Hn7zhW+QarWy9qr/7P7YMj3p1IaGfFjssSJmH4lglacA4Cgv7fyekzqRA3 9IAAhSl5rxl6OEOf8O4boHQ9d/6rIbxQED2WUo9ZYrp1hCI5B0y9rPakrZQR 3MzFlfgMMp; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: pk@denic.de, vijay@wichorus.com, dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 24 Apr 2009 05:24:36 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-175-250540280 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable On 24 apr 2009, at 01.25, wrote: >> b) Do you want to use DDDS or Bonjour algorithm >> b: You want bonjour, as what you do is a more zeroconf algorithm > > My limited understanding of the Bonjour algorithm tells me that it =20 > only works in the local network. Since the Mobility Servers would =20 > need to be discovered also in remote networks, I'd prefer a more =20 > general solution. Absolutely not. There is one algorithm for local network (you send DNS =20= queries over IP multicast), and one for wide area bonjour. >> a) Is it correct to use the search domain for usage like >> this (in a DDDS context) and Bonjour >> a: Yes - but we need a generic document that updates the DNS >> spec that talk about this change > > I assume you mean the usage of search_domain/home_domain as the =20 > first valid key to the DDDS application. Yes, or as seed for the wide area bonjour algorithm. > I'd be willing to go down this path if the community finds it =20 > acceptable. Patrik > > Thanks, > - Gabor > > >> -----Original Message----- >> From: ext Patrik F=E4ltstr=F6m [mailto:paf@cisco.com] >> Sent: Thursday, April 23, 2009 12:10 AM >> To: Bajko Gabor (Nokia-CIC/MtView) >> Cc: pk@denic.de; jari.arkko@piuha.net; vijay@wichorus.com; >> dns-dir@ietf.org >> Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues >> >> >> On 22 apr 2009, at 00.57, wrote: >> >>> Hi Peter, Patrik >>> >>>> The crucial point in the draft is: >>>> >>>> The procedures defined here assume that the MN knows the >> domain name >>>> of the network where it wants to locate a Mobility Server. The >>>> domain name of the network can either be pre-configured, >> discovered >>>> >>>> This assumes that "a network" has "a domain name", which >> I disagree >>>> with. >>> >>> Would the below re-write of the paragraph you cite above solve the >>> problem? >>> >>> The procedures defined in this document assume that the MN >> knows the >>> search domain (DNS suffix) where it wants to locate a >> Mobility Server. >> >> I think we have two problems here. >> >> a) Is it correct to use the search domain for usage like >> this (in a DDDS context) and Bonjour >> >> b) Do you want to use DDDS or Bonjour algorithm >> >> I think personally the answers are: >> >> a: Yes - but we need a generic document that updates the DNS >> spec that talk about this change >> >> b: You want bonjour, as what you do is a more zeroconf algorithm >> >> Other people cc:ed might have different opinion. >> >> >> Patrik >> >>> When the MN wants to find Mobility Servers in its current visited >>> network, it can use DHCP option 15 to request the domain name it >>> should use when resolving hostnames via DNS. The domain >> name suffix >>> returned in the option can be used as the search domain. >>> When the MN wants to find Mobility Servers in the home >> network, it can >>> use the home domain of its subscription as the search domain. >>> If the MN wants to find Mobility Servers in a 3rd party operated >>> network (which is not its current visited, or its home network) it >>> needs to have the search domains of those 3rd party >> operated networks >>> preconfigured, or use IEEE 802.21 Information Service query >>> [IEEE802.21] to find the home domains of the networks >> operating in the >>> location of interest. >>> >>> The naming issues mentioned by Patrik in the other mail >> can easily be >>> addressed. >>> >>> Using the Bonjour way in my opinion wouldn't solve the >> issue as it has >>> the same problem, ie how to find the suffix of the search domain. >>> >>> Thanks, >>> - gabor >>> >>> >>>> -----Original Message----- >>>> From: Peter Koch [mailto:peter@denic.de] On Behalf Of ext >> Peter Koch >>>> Sent: Monday, April 20, 2009 5:08 AM >>>> To: Jari Arkko >>>> Cc: dns directorate; Bajko Gabor (Nokia); Devarapalli, Vijay >>>> Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues >>>> >>>> Jari, >>>> >>>>> I have a document in AD review >>>> (draft-ietf-mipshop-mos-dns-discovery) >>>>> where I had a number of question marks relating to the use and >>>>> registration of NATPTRs. I also asked Leslie Daigle for >>>> some help and >>>>> she suggested S-NAPTR might have been a more appropriate >>>> tool for this >>>>> task. The problem is, she is busy and I'm clueless about >>>> NAPTR. I'd >>>>> like to find one volunteer with such clue from the >>>> directorate, and >>>>> put the volunteer, me, and the author and chair (Cced) >> to the same >>>>> conference call sometime this or next week. The volunteer >>>> should help >>>>> us understand whether something needs to change in the >>>> document, and if so, what. >>>> >>>> I vaguely remembered I had reviewed this draft in an >> earlier version. >>>> NAPTR RRs are defined in the DDDS context only and for less >>>> structured or specialized name spaces ther are S-NAPTR >> and U-NAPTR. >>>> I am not a particular fan of either one because I don't >> believe in >>>> DNS as a service discovery (rather than a service location) >>>> mechanism. >>>> >>>> The crucial point in the draft is: >>>> >>>> The procedures defined here assume that the MN knows the >> domain name >>>> of the network where it wants to locate a Mobility Server. The >>>> domain name of the network can either be pre-configured, >> discovered >>>> >>>> This assumes that "a network" has "a domain name", which >> I disagree >>>> with. >>>> Apart from that IO'd be willing to help, of course. If >> any of you is >>>> going to be at the RIPE meeting early May, that would >> even allow a >>>> face 2 face discussion. >>>> >>>> -Peter >>>> >>> _______________________________________________ >>> dns-dir mailing list >>> dns-dir@ietf.org >>> https://www.ietf.org/mailman/listinfo/dns-dir >> >> --Apple-Mail-175-250540280 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) iD8DBQFJ8U1ZvHlR2X0luNwRAhTDAJ9Pb2P4ZhcP9tV04MmZ7cENxGSfgACfTV6+ d7YbZKfx2rysehTGZVCWRCg= =MCcL -----END PGP SIGNATURE----- --Apple-Mail-175-250540280-- From jari.arkko@piuha.net Fri Apr 24 05:04:02 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 DE03C3A6B17 for ; Fri, 24 Apr 2009 05:04:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.26 X-Spam-Level: X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=0.039, 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 X2mnSUVDI2nq for ; Fri, 24 Apr 2009 05:04:02 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 26EEB3A6AB3 for ; Fri, 24 Apr 2009 05:04:02 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 2C22A1986EE; Fri, 24 Apr 2009 15:05:20 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id DF933198686; Fri, 24 Apr 2009 15:05:19 +0300 (EEST) Message-ID: <49F1AAEA.8040601@piuha.net> Date: Fri, 24 Apr 2009 15:04:58 +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?= , Gabor.Bajko@nokia.com, pk@denic.de, vijay@wichorus.com References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 24 Apr 2009 12:04:03 -0000 How about a phone call to talk about this? Please fill in the poll here: http://www.doodle.com/pg5nxaxi27s9bmky Jari From ogud@ogud.com Fri Apr 24 11:28: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 9BC5B3A6F95 for ; Fri, 24 Apr 2009 11:28:44 -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 MgXJo8IhRsab for ; Fri, 24 Apr 2009 11:28:43 -0700 (PDT) Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by core3.amsl.com (Postfix) with ESMTP id A3E1328C1A9 for ; Fri, 24 Apr 2009 11:28: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 n3OIU1ft039225 for ; Fri, 24 Apr 2009 14:30:01 -0400 (EDT) (envelope-from ogud@ogud.com) To: dns-dir@ietf.org From: Olafur_DNS_EARLY_WARNING Date: Fri, 24 Apr 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: <20090424_183001_005565.ogud@ogud.com> X-Scanned-By: MIMEDefang 2.64 on 66.92.146.20 Subject: [dns-dir] DNS Early Warn: draft-xli-behave-v4v6-prefix-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, 24 Apr 2009 18:28:44 -0000 Count: 18 behave X. Li, Ed. Internet-Draft C. Bao, Ed. Intended status: Standards Track CERNET Center/Tsinghua University Expires: October 24, 2009 F. Baker, Ed. Cisco Systems April 22, 2009 IPv4/IPv6 Translation Prefix Recommendation draft-xli-behave-v4v6-prefix-00 Abstract This document is part of a series of the IPv4/IPv6 translation documents. In this document, the address format and the corresponding prefix are recommended for representing IPv4 addresses in IPv6 and/or for representing IPv6 addresses in IPv4. From Gabor.Bajko@nokia.com Thu Apr 23 16:24: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 395823A6E39 for ; Thu, 23 Apr 2009 16:24:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.299 X-Spam-Level: X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 UuovNxnl+ACG for ; Thu, 23 Apr 2009 16:24:52 -0700 (PDT) Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 84D893A6923 for ; Thu, 23 Apr 2009 16:24:51 -0700 (PDT) Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n3NNPVl6025314; Fri, 24 Apr 2009 02:25:52 +0300 Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 24 Apr 2009 02:25:33 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 24 Apr 2009 02:25:28 +0300 Received: from NOK-AM1MHUB-05.mgdnok.nokia.com (65.54.30.9) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 24 Apr 2009 01:25:28 +0200 Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by NOK-AM1MHUB-05.mgdnok.nokia.com ([65.54.30.9]) with mapi; Fri, 24 Apr 2009 01:25:28 +0200 From: To: Date: Fri, 24 Apr 2009 01:25:24 +0200 Thread-Topic: [dns-dir] help with NAPTR & S-NAPTR issues Thread-Index: AcnD4odW7fsRGsv+Q3SpQJQ62cmkowAhGYBQ Message-ID: References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> In-Reply-To: <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 23 Apr 2009 23:25:28.0837 (UTC) FILETIME=[C9D29B50:01C9C46A] X-Nokia-AV: Clean X-Mailman-Approved-At: Sat, 25 Apr 2009 13:44:14 -0700 Cc: pk@denic.de, vijay@wichorus.com, dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 23 Apr 2009 23:24:53 -0000 Hi Patrik, >b) Do you want to use DDDS or Bonjour algorithm >b: You want bonjour, as what you do is a more zeroconf algorithm My limited understanding of the Bonjour algorithm tells me that it only wor= ks in the local network. Since the Mobility Servers would need to be discov= ered also in remote networks, I'd prefer a more general solution. >a) Is it correct to use the search domain for usage like=20 >this (in a DDDS context) and Bonjour >a: Yes - but we need a generic document that updates the DNS=20 >spec that talk about this change I assume you mean the usage of search_domain/home_domain as the first valid= key to the DDDS application. I'd be willing to go down this path if the community finds it acceptable. Thanks, - Gabor >-----Original Message----- >From: ext Patrik F=E4ltstr=F6m [mailto:paf@cisco.com]=20 >Sent: Thursday, April 23, 2009 12:10 AM >To: Bajko Gabor (Nokia-CIC/MtView) >Cc: pk@denic.de; jari.arkko@piuha.net; vijay@wichorus.com;=20 >dns-dir@ietf.org >Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues > > >On 22 apr 2009, at 00.57, wrote: > >> Hi Peter, Patrik >> >>> The crucial point in the draft is: >>> >>> The procedures defined here assume that the MN knows the=20 >domain name =20 >>> of the network where it wants to locate a Mobility Server. The =20 >>> domain name of the network can either be pre-configured,=20 >discovered >>> >>> This assumes that "a network" has "a domain name", which=20 >I disagree=20 >>> with. >> >> Would the below re-write of the paragraph you cite above solve the=20 >> problem? >> >> The procedures defined in this document assume that the MN=20 >knows the=20 >> search domain (DNS suffix) where it wants to locate a=20 >Mobility Server. > >I think we have two problems here. > >a) Is it correct to use the search domain for usage like=20 >this (in a DDDS context) and Bonjour > >b) Do you want to use DDDS or Bonjour algorithm > >I think personally the answers are: > >a: Yes - but we need a generic document that updates the DNS=20 >spec that talk about this change > >b: You want bonjour, as what you do is a more zeroconf algorithm > >Other people cc:ed might have different opinion. > > > Patrik > >> When the MN wants to find Mobility Servers in its current visited=20 >> network, it can use DHCP option 15 to request the domain name it=20 >> should use when resolving hostnames via DNS. The domain=20 >name suffix=20 >> returned in the option can be used as the search domain. >> When the MN wants to find Mobility Servers in the home=20 >network, it can=20 >> use the home domain of its subscription as the search domain. >> If the MN wants to find Mobility Servers in a 3rd party operated=20 >> network (which is not its current visited, or its home network) it=20 >> needs to have the search domains of those 3rd party=20 >operated networks=20 >> preconfigured, or use IEEE 802.21 Information Service query=20 >> [IEEE802.21] to find the home domains of the networks=20 >operating in the=20 >> location of interest. >> >> The naming issues mentioned by Patrik in the other mail=20 >can easily be=20 >> addressed. >> >> Using the Bonjour way in my opinion wouldn't solve the=20 >issue as it has=20 >> the same problem, ie how to find the suffix of the search domain. >> >> Thanks, >> - gabor >> >> >>> -----Original Message----- >>> From: Peter Koch [mailto:peter@denic.de] On Behalf Of ext=20 >Peter Koch >>> Sent: Monday, April 20, 2009 5:08 AM >>> To: Jari Arkko >>> Cc: dns directorate; Bajko Gabor (Nokia); Devarapalli, Vijay >>> Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues >>> >>> Jari, >>> >>>> I have a document in AD review >>> (draft-ietf-mipshop-mos-dns-discovery) >>>> where I had a number of question marks relating to the use and=20 >>>> registration of NATPTRs. I also asked Leslie Daigle for >>> some help and >>>> she suggested S-NAPTR might have been a more appropriate >>> tool for this >>>> task. The problem is, she is busy and I'm clueless about >>> NAPTR. I'd >>>> like to find one volunteer with such clue from the >>> directorate, and >>>> put the volunteer, me, and the author and chair (Cced)=20 >to the same=20 >>>> conference call sometime this or next week. The volunteer >>> should help >>>> us understand whether something needs to change in the >>> document, and if so, what. >>> >>> I vaguely remembered I had reviewed this draft in an=20 >earlier version. >>> NAPTR RRs are defined in the DDDS context only and for less=20 >>> structured or specialized name spaces ther are S-NAPTR=20 >and U-NAPTR. =20 >>> I am not a particular fan of either one because I don't=20 >believe in=20 >>> DNS as a service discovery (rather than a service location)=20 >>> mechanism. >>> >>> The crucial point in the draft is: >>> >>> The procedures defined here assume that the MN knows the=20 >domain name =20 >>> of the network where it wants to locate a Mobility Server. The =20 >>> domain name of the network can either be pre-configured,=20 >discovered >>> >>> This assumes that "a network" has "a domain name", which=20 >I disagree=20 >>> with. >>> Apart from that IO'd be willing to help, of course. If=20 >any of you is=20 >>> going to be at the RIPE meeting early May, that would=20 >even allow a=20 >>> face 2 face discussion. >>> >>> -Peter >>> >> _______________________________________________ >> dns-dir mailing list >> dns-dir@ietf.org >> https://www.ietf.org/mailman/listinfo/dns-dir > >= From erik.nordmark@sun.com Sun Apr 26 21:56:14 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 88D3A3A67A8 for ; Sun, 26 Apr 2009 21:56:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.529 X-Spam-Level: X-Spam-Status: No, score=-5.529 tagged_above=-999 required=5 tests=[AWL=0.517, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 Pd7sczIy8Jjz for ; Sun, 26 Apr 2009 21:56:13 -0700 (PDT) Received: from sca-ea-mail-1.sun.com (sca-ea-mail-1.Sun.COM [192.18.43.24]) by core3.amsl.com (Postfix) with ESMTP id 3D0353A6DF2 for ; Sun, 26 Apr 2009 21:55:59 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.228.31]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3R4vEnl012843; Mon, 27 Apr 2009 04:57:14 GMT Received: from [10.7.251.248] (punchin-nordmark.SFBay.Sun.COM [10.7.251.248]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3R4vBQP110587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Apr 2009 21:57:12 -0700 (PDT) Message-ID: <49F53B27.5000604@sun.com> Date: Sun, 26 Apr 2009 21:57:11 -0700 From: Erik Nordmark User-Agent: Thunderbird 2.0.0.18 (X11/20090211) MIME-Version: 1.0 To: Peter Koch References: <200904061412.n36ECfip043004@stora.ogud.com> <20090406160517.GB30703@x27.adm.denic.de> In-Reply-To: <20090406160517.GB30703@x27.adm.denic.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Anybody else trying to call in ? 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, 27 Apr 2009 04:56:14 -0000 Peter Koch wrote: > On Mon, Apr 06, 2009 at 10:12:34AM -0400, Olafur Gudmundsson wrote: >> I hear only music, with periodic message that we are waiting for chair >> person to dial in. > > since this was short after the San Francisco IETF, I had suggested to skip > this call and move the next one from early May (collision with the RIPE > meeting) to 2008-04-27 1400 UTC. Apologies if my badly chosen subject > line confused you. Do we have an agenda for tomorrow? Erik From jari.arkko@piuha.net Mon Apr 27 01:41:29 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 80A6C3A6962 for ; Mon, 27 Apr 2009 01:41:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.321 X-Spam-Level: X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=-0.022, 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 IrN7jaejBmRU for ; Mon, 27 Apr 2009 01:41:28 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id BFA353A63EB for ; Mon, 27 Apr 2009 01:41:27 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id E769919877B; Mon, 27 Apr 2009 11:42:47 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id A7532198671; Mon, 27 Apr 2009 11:42:47 +0300 (EEST) Message-ID: <49F56FEF.1030703@piuha.net> Date: Mon, 27 Apr 2009 11:42:23 +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?= , Gabor.Bajko@nokia.com, pk@denic.de, vijay@wichorus.com References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> <49F1AAEA.8040601@piuha.net> In-Reply-To: <49F1AAEA.8040601@piuha.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 27 Apr 2009 08:41:29 -0000 Lets pick Wednesday 3 PM CET: Conference Title: mipshop naptr Additional Information: Web booked conference Number of Participants: 10 Conference Duration: 90 Date of Conference: 29-Apr-09 Recurring Conference: No Start Time: 15:00 Timezone: Stockholm, Sweden Recording: No Participant Code: 78959 Conference Phone Numbers: +1 972 583 9950 , 866-523-2663, ECN: 800 39950 , *Toll Free: 866-52 ECONF* ., Conference Helpline: +1 972 583 4444 Jari Jari Arkko wrote: > How about a phone call to talk about this? Please fill in the poll here: > > http://www.doodle.com/pg5nxaxi27s9bmky > > Jari > > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir > > From pfaltstr@cisco.com Mon Apr 27 02:37:12 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 0DEF43A6A6D for ; Mon, 27 Apr 2009 02:37:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.721 X-Spam-Level: X-Spam-Status: No, score=-6.721 tagged_above=-999 required=5 tests=[AWL=-0.422, 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 870CGcoTzGrP for ; Mon, 27 Apr 2009 02:37:11 -0700 (PDT) Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 28E043A6A5F for ; Mon, 27 Apr 2009 02:37:11 -0700 (PDT) X-Files: PGP.sig : 186 X-IronPort-AV: E=Sophos;i="4.40,253,1238976000"; d="sig'?scan'208";a="177220717" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by sj-iport-1.cisco.com with ESMTP; 27 Apr 2009 09:38:29 +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 n3R9cT4X016096; Mon, 27 Apr 2009 11:38:29 +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 n3R9cTT4025154; Mon, 27 Apr 2009 09:38:29 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Apr 2009 11:38:29 +0200 Received: from [192.168.1.129] ([10.61.83.145]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Apr 2009 11:38:28 +0200 Message-Id: From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: Jari Arkko In-Reply-To: <49F56FEF.1030703@piuha.net> Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-36-524902448" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 27 Apr 2009 11:38:27 +0200 References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> <49F1AAEA.8040601@piuha.net> <49F56FEF.1030703@piuha.net> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 27 Apr 2009 09:38:28.0788 (UTC) FILETIME=[EB9EFF40:01C9C71B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1609; t=1240825109; x=1241689109; 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]=20help=20with=20NAPTR=20&=20S -NAPTR=20issues |Sender:=20; bh=AAX3DnejplOCPArwphpP5vskYBZ3sO966CFLE4x2o/k=; b=maW0y7SLT1vIn1Fr+sjqYch3FKUobbMbPyXqmkWtC/eFmdIJ4FG7EVLce1 9QG7K91Y00ECrDbczf3AqlG0vPcx6gOP4LAE0DPzqa26Mp+PkzYdZe8/lLxN pGnzDFhfC6; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: Gabor.Bajko@nokia.com, pk@denic.de, vijay@wichorus.com, dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 27 Apr 2009 09:37:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-36-524902448 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Ok! paf On 27 apr 2009, at 10.42, Jari Arkko wrote: > Lets pick Wednesday 3 PM CET: > > Conference Title: mipshop naptr Additional Information: > Web booked conference > Number of Participants: 10 Conference Duration: 90 > Date of Conference: 29-Apr-09 Recurring Conference: No > Start Time: 15:00 Timezone: Stockholm, Sweden > Recording: No Participant Code: 78959 > Conference Phone Numbers: +1 972 583 9950 , 866-523-2663, > ECN: 800 39950 , *Toll Free: 866-52 ECONF* ., Conference Helpline: > +1 972 583 4444 > > Jari > > Jari Arkko wrote: >> How about a phone call to talk about this? Please fill in the poll >> here: >> >> http://www.doodle.com/pg5nxaxi27s9bmky >> >> Jari >> >> _______________________________________________ >> dns-dir mailing list >> dns-dir@ietf.org >> https://www.ietf.org/mailman/listinfo/dns-dir >> >> > --Apple-Mail-36-524902448 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) iD8DBQFJ9X0TvHlR2X0luNwRAiUxAJ9n96Wec9DIC4jY9f7HJ3aX7LFm9ACgroIP aH5gCBzJvI/t6fP7BKe8Gmk= =oKzN -----END PGP SIGNATURE----- --Apple-Mail-36-524902448-- From dromasca@avaya.com Mon Apr 27 03:18:20 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 4E8043A6A35 for ; Mon, 27 Apr 2009 03:18:20 -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 NqRfUNJdgtQt for ; Mon, 27 Apr 2009 03:18:19 -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 230203A685A for ; Mon, 27 Apr 2009 03:18:18 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,253,1238990400"; d="scan'208";a="144167360" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 27 Apr 2009 06:19:37 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 27 Apr 2009 06:19:36 -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: Mon, 27 Apr 2009 12:19:35 +0200 Message-ID: In-Reply-To: <49F53B27.5000604@sun.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [dns-dir] Anybody else trying to call in ? Thread-Index: AcnG9LEF4mkW/0PERKuiaS010hfgWwALOJ+w References: <200904061412.n36ECfip043004@stora.ogud.com><20090406160517.GB30703@x27.adm.denic.de> <49F53B27.5000604@sun.com> From: "Romascanu, Dan (Dan)" To: "Erik Nordmark" , "Peter Koch" Cc: dns-dir@ietf.org Subject: Re: [dns-dir] Anybody else trying to call in ? 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, 27 Apr 2009 10:18:20 -0000 Do we have a conference number and code?=20 Dan =20 > -----Original Message----- > From: dns-dir-bounces@ietf.org=20 > [mailto:dns-dir-bounces@ietf.org] On Behalf Of Erik Nordmark > Sent: Monday, April 27, 2009 7:57 AM >=20 > Do we have an agenda for tomorrow? >=20 > Erik From peter@denic.de Mon Apr 27 05:47: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 B15BD3A6D61 for ; Mon, 27 Apr 2009 05:47:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.011 X-Spam-Level: X-Spam-Status: No, score=-6.011 tagged_above=-999 required=5 tests=[AWL=0.238, 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 e8lYCD0xyl6m for ; Mon, 27 Apr 2009 05:47:22 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id DFFF93A6929 for ; Mon, 27 Apr 2009 05:47:21 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1LyQGG-0001fR-QL; Mon, 27 Apr 2009 14:48:40 +0200 Received: from localhost by x27.adm.denic.de with local id 1LyQCy-0006sb-Ti; Mon, 27 Apr 2009 14:45:16 +0200 Date: Mon, 27 Apr 2009 14:45:16 +0200 From: Peter Koch To: dns-dir@ietf.org Message-ID: <20090427124516.GE11204@x27.adm.denic.de> References: <49F53B27.5000604@sun.com> 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 Subject: Re: [dns-dir] Anybody else trying to call in ? 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, 27 Apr 2009 12:47:22 -0000 DNS-Dir, the two agenda item that I'd like to suggest are: 1) Administrative Issues - Mailing list overhaul (archive access) 2) Open DNS-Dir Reviews - any outstanding document reviews? - any outstanding wg charter reviews? > Do we have a conference number and code? That's a bit more difficult. I'd suggest to try the same data as "last time", but not sure I can get access to the "session leader" code. -Peter From dromasca@avaya.com Mon Apr 27 06:27:25 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 513FB3A6929 for ; Mon, 27 Apr 2009 06:27:25 -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 jmLscANniJiW for ; Mon, 27 Apr 2009 06:27:24 -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 733313A6D97 for ; Mon, 27 Apr 2009 06:27:24 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,254,1238990400"; d="scan'208";a="169113225" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 27 Apr 2009 09:28:44 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 27 Apr 2009 09:28: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: Mon, 27 Apr 2009 15:28:41 +0200 Message-ID: In-Reply-To: <20090427124516.GE11204@x27.adm.denic.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [dns-dir] Anybody else trying to call in ? Thread-Index: AcnHNoJPb+6HEhbbRwyqofP8rh97ZwABYCsQ References: <49F53B27.5000604@sun.com> <20090427124516.GE11204@x27.adm.denic.de> From: "Romascanu, Dan (Dan)" To: "Peter Koch" , Subject: Re: [dns-dir] Anybody else trying to call in ? 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, 27 Apr 2009 13:27:25 -0000 Can you remind me the last time information? Dan =20 > -----Original Message----- > From: dns-dir-bounces@ietf.org=20 > [mailto:dns-dir-bounces@ietf.org] On Behalf Of Peter Koch > Sent: Monday, April 27, 2009 3:45 PM > To: dns-dir@ietf.org > Subject: Re: [dns-dir] Anybody else trying to call in ? >=20 > DNS-Dir, >=20 > the two agenda item that I'd like to suggest are: >=20 > 1) Administrative Issues > - Mailing list overhaul (archive access) >=20 > 2) Open DNS-Dir Reviews > - any outstanding document reviews? > - any outstanding wg charter reviews? >=20 > > Do we have a conference number and code?=20 >=20 > That's a bit more difficult. I'd suggest to try the same=20 > data as "last time", but not sure I can get access to the=20 > "session leader" code. >=20 > -Peter > _______________________________________________ > dns-dir mailing list > dns-dir@ietf.org > https://www.ietf.org/mailman/listinfo/dns-dir >=20 From ajs@shinkuro.com Mon Apr 27 06:40:21 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 A8BC33A6F72 for ; Mon, 27 Apr 2009 06:40:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.799 X-Spam-Level: X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=0.800, 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 VlhoBx-ZSHKG for ; Mon, 27 Apr 2009 06:40:20 -0700 (PDT) Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id D8E3B3A6C19 for ; Mon, 27 Apr 2009 06:40:20 -0700 (PDT) Received: from crankycanuck.ca (CPE00212980eb9c-CM00194757af08.cpe.net.cable.rogers.com [99.249.242.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id B21E52FE960A for ; Mon, 27 Apr 2009 13:41:40 +0000 (UTC) Date: Mon, 27 Apr 2009 09:41:39 -0400 From: Andrew Sullivan To: dns-dir@ietf.org Message-ID: <20090427134139.GC73201@shinkuro.com> References: <20090427124516.GE11204@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.5.18 (2008-05-17) Subject: Re: [dns-dir] Anybody else trying to call in ? 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, 27 Apr 2009 13:40:21 -0000 On Mon, Apr 27, 2009 at 03:28:41PM +0200, Romascanu, Dan (Dan) wrote: > Can you remind me the last time information? I don't know it either, so if we could have it on list, that'd help. A -- Andrew Sullivan ajs@shinkuro.com Shinkuro, Inc. From pfaltstr@cisco.com Tue Apr 28 10:32: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 18D323A70DC for ; Tue, 28 Apr 2009 10:32:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.674 X-Spam-Level: X-Spam-Status: No, score=-7.674 tagged_above=-999 required=5 tests=[AWL=0.558, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067] 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 heJyiWnwCVBy for ; Tue, 28 Apr 2009 10:32:22 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A7A4E3A70A3 for ; Tue, 28 Apr 2009 10:32:21 -0700 (PDT) X-Files: PGP.sig : 186 X-IronPort-AV: E=Sophos;i="4.40,261,1238976000"; d="sig'?scan'208";a="39342275" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 28 Apr 2009 17:33:42 +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 n3SHXgZQ022008; Tue, 28 Apr 2009 19:33:42 +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 n3SHXgjf021416; Tue, 28 Apr 2009 17:33:42 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 28 Apr 2009 19:33:42 +0200 Received: from 94.191.170.53.bredband.tre.se ([10.61.98.231]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 28 Apr 2009 19:33:40 +0200 Message-Id: <6972AB50-B672-4694-AE42-C1E867B7F7DE@cisco.com> From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: Jari Arkko In-Reply-To: <49F56FEF.1030703@piuha.net> Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-102-639812581" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 28 Apr 2009 19:33:37 +0200 References: <49EC60A7.2000208@piuha.net> <20090420120800.GJ12052@x27.adm.denic.de> <9896F74D-BFB9-477B-AC74-24F73142100F@cisco.com> <49F1AAEA.8040601@piuha.net> <49F56FEF.1030703@piuha.net> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 28 Apr 2009 17:33:41.0226 (UTC) FILETIME=[78C584A0:01C9C827] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1856; t=1240940022; x=1241804022; 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]=20help=20with=20NAPTR=20&=20S -NAPTR=20issues |Sender:=20; bh=cez/muBz2T4TvJJcM1lDHxna+KSNqSED+JUSdxkN34Q=; b=RJm2ozmnXegFtHUT3cOtsRByVEjdF5CoKg8Y9odN0ZQrhMtOsNU22ASG13 apviPCNb72PMsri3bSJgqeLNe8QUa0kIqqZQve/aJWwCw/hQCG6MY2wLlAEZ wVjAPKUmFs; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: Gabor.Bajko@nokia.com, pk@denic.de, vijay@wichorus.com, dns-dir@ietf.org Subject: Re: [dns-dir] help with NAPTR & S-NAPTR issues 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, 28 Apr 2009 17:32:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-102-639812581 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Hmm...I just got a very urgent call with ISOC re. ICANN at this time slot that seems to be very hard to move. Can we move this 30 min earlier? As I do not think we need more time than 30 min for me to clarify what I think the issue is? Patrik On 27 apr 2009, at 10.42, Jari Arkko wrote: > Lets pick Wednesday 3 PM CET: > > Conference Title: mipshop naptr Additional Information: > Web booked conference > Number of Participants: 10 Conference Duration: 90 > Date of Conference: 29-Apr-09 Recurring Conference: No > Start Time: 15:00 Timezone: Stockholm, Sweden > Recording: No Participant Code: 78959 > Conference Phone Numbers: +1 972 583 9950 , 866-523-2663, > ECN: 800 39950 , *Toll Free: 866-52 ECONF* ., Conference Helpline: > +1 972 583 4444 > > Jari > > Jari Arkko wrote: >> How about a phone call to talk about this? Please fill in the poll >> here: >> >> http://www.doodle.com/pg5nxaxi27s9bmky >> >> Jari >> >> _______________________________________________ >> dns-dir mailing list >> dns-dir@ietf.org >> https://www.ietf.org/mailman/listinfo/dns-dir >> >> > --Apple-Mail-102-639812581 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) iD8DBQFJ9z3xvHlR2X0luNwRAp9ZAJ9DPDJWzhFMufBF1kaAb0NlUtQZJgCeL1FT nzxWTNurG9VJOKO5qQy7BC4= =7Ue8 -----END PGP SIGNATURE----- --Apple-Mail-102-639812581--