From apache@ticket.ietf.org Tue Oct 30 15:11:09 2007 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from ticket.ietf.org (ticket.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l9UMAIgA016723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 30 Oct 2007 15:10:19 -0700 (PDT) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1ImzHu-0005Yi-2C for rfc-editor@rfc-editor.org; Tue, 30 Oct 2007 18:10:18 -0400 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #97698 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Tue, 30 Oct 2007 18:10:18 -0400 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #97698] AutoReply: Informational (IRTF) Independent Submission: draft-irtf-tmrg-metrics-11.txt X-IMAPbase: 1225308294 98 $NotJunk $Junk Status: O X-Status: X-Keywords: $NotJunk X-UID: 1 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Informational (IRTF) Independent Submission: draft-irtf-tmrg-metrics-11.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #97698] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #97698] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-irtf-tmrg-metrics-11.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 26 November 2007. Metrics for the Evaluation of Congestion Control Mechanisms This document discusses the metrics to be considered in an evaluation of new or modified congestion control mechanisms for the Internet. These include metrics for the evaluation of new transport protocols, of proposed modifications to TCP, of application-level congestion control, and of Active Queue Management (AQM) mechanisms in the router. This document is the first in a series of documents aimed at improving the models that we use in the evaluation of transport protocols. This document is a product of the Transport Modeling Research Group (TMRG), and has received detailed feedback from many members of the Research Group (RG). As the document tries to make clear, there is not necessarily a consensus within the research community (or the IETF community, the vendor community, the operations community, or any other community) about the metrics that congestion control mechanisms should be designed to optimize, in terms of tradeoffs between throughput and delay, fairness between competing flows, and the like. However, we believe that there is a clear consensus that congestion control mechanisms should be evaluated in terms of tradeoffs between a range of metrics, rather than in terms of optimizing for a single metric. Note: Please see the email below for more details regarding the review that this document has received. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents On Tue, Oct 23, 2007 at 09:22:38PM -0400, Aaron Falk wrote: > Dear RFC Editor- > > Please publish draft-irtf-tmrg-metrics-11 as an Informational IRTF- > stream RFC. The IRSG has reviewed this document and approved it for > publication. Please include Sally Floyd on all > correspondence relating to publication of this document. Details of > the review process follow below. > > --Aaron Falk > IRTF Chair > > > Begin forwarded message: > > >From: Sally Floyd > >Date: October 23, 2007 8:21:42 PM EDT > >To: Aaron Falk , Internet Research Steering Group > > > >Subject: TMRG metrics document ready to send to RFC editor > > > >Aaron - > > > >In accordance with current IRTF processes, the TMRG metrics > >document [1] is now finished IRSG review and ready for you > >to send to the RFC editor. > > > >The tracker ticket [2] for this has links to various stages of > >the review, including links to the June review from Tony Li [3] and > >feedback from Juergen Schoenwaelder [4]. The follow-up email [5] > >reports the Ready-to-Publish votes from Juergen Schoenwaelder and > >Aaron Falk, and the changes in the document to address the feedback > >received. Email from the RG can be found on the TMRG mailing list > >[6, 7, 8, 9, 10, 11]. > > > >I'll be shepherd for this document which is intended to become > >an informational RFC. > > > >[1] http://www.icir.org/tmrg/draft-irtf-tmrg-metrics-11.txt > > http://www.icir.org/tmrg/draft-irtf-tmrg-metrics-11.ps > >[2] http://www1.tools.ietf.org/group/irtf/trac/ticket/11 > >[3] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2007- > >June/000150.html > >[4] http://www3.tools.ietf.org/group/irtf/trac/attachment/ticket/11/ > >Schoenwaelder-review.txt > >[5] http://www3.tools.ietf.org/group/irtf/trac/attachment/ticket/11/ > >Floyd-Oct-3-2007.txt > >[6] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2006- > >November/000133.html > >[7] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2007- > >February/000135.html > >[8] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2007- > >March/000138.html > >[9] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2007- > >March/000141.html > >[10] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2007- > >September/000166.html > >[11] http://mailman.icsi.berkeley.edu/pipermail/tmrg-interest/2007- > >September/000188.html > > > >Regards, > >- Sally > >http://www.icir.org/floyd/ > > From apache@ticket.ietf.org Thu Nov 8 12:52:20 2007 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id lA8Kpnam012522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 8 Nov 2007 12:51:49 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1IqELs-0008ON-Hl for rfc-editor@rfc-editor.org; Thu, 08 Nov 2007 15:51:48 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #97880 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Thu, 08 Nov 2007 15:51:48 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #97880] AutoReply: Informational Independent Submission: draft-jayasumana-reorder-density-07.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 2 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Informational Independent Submission: draft-jayasumana-reorder-density-07.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #97880] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #97880] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-jayasumana-reorder-density-07.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Five week timeout expires on 13 December 2007. We have included an additional week because of the upcoming IETF. Reorder Density and Reorder Buffer-occupancy Density - Metrics for Packet Reordering Measurements This document presents two metrics for packet reordering, namely, Reorder Density (RD) and Reorder Buffer-occupancy Density (RBD). A threshold is used to clearly define when a packet is considered lost, to bound computational complexity at O(N), and to keep the memory requirement for evaluation independent of N, where N is the length of the packet sequence. RD is a comprehensive metric that captures the characteristics of reordering, while RBD evaluates the sequences from the point of view of recovery from reordering. These metrics are simple to compute yet comprehensive in their characterization of packet reordering. The measures are robust and orthogonal to packet loss and duplication. This document was reviewed by Craig Partridge (twice) and significantly updated as a result. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From apache@ticket.ietf.org Wed Nov 21 14:37:14 2007 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from ticket.ietf.org (ticket.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id lALMaFNp015522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 21 Nov 2007 14:36:16 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1IuyB5-000158-3l for rfc-editor@rfc-editor.org; Wed, 21 Nov 2007 17:36:15 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98125 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 21 Nov 2007 17:36:15 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98125] AutoReply: Exerpimental (IRTF) Independent Submission: draft-irtf-mobopts-l2-abstractions-04.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 3 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Exerpimental (IRTF) Independent Submission: draft-irtf-mobopts-l2-abstractions-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98125] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98125] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Experimental: draft-irtf-mobopts-l2-abstractions-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Five week timeout expires on 26 December 2007. (Note that this is a 5 week timeout because of the upcoming IETF.) Unified L2 Abstractions for L3-Driven Fast Handover This draft proposes unified L2 abstractions for L3-driven fast handovers. For efficient network communication, it is vital for a protocol layer to know or utilize other layer's information such as a form of L2 triggers. However, each protocol layer is basically designed independently. Since each protocol layer is also implemented independently in current operating systems, it is very hard to exchange control information between protocol layers. This draft defines nine kinds of L2 abstractions in the form of "primitives" to achieve fast handovers in the network layer as a means of solving the problem. This mechanism is called "L3-driven fast handovers" because the network layer initiates L2 and L3 handovers by using the "primitives". This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. Please note that the email below provides additional information about the review this document has received. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents ----- Forwarded message from Aaron Falk ----- Cc: Internet Research Steering Group , Rajeev Koodli , mobopts@irtf.org From: Aaron Falk Subject: Request to publish draft-irtf-mobopts-l2-abstractions-04 as an IRTF RFC Date: Wed, 21 Nov 2007 10:23:52 -0500 To: RFC Editor Dear RFC Editor- Please publish draft-irtf-mobopts-l2-abstractions-04 as an Experimental IRTF-stream RFC. The IRSG has reviewed this document and approved it for publication. Please include Rajeev Koodli on all correspondence relating to publication of this document. Details of the review process follow below. Also, please make the two small edits are requested below. Regards, --Aaron Falk IRTF Chair Begin forwarded message: >From: Rajeev Koodli >Date: November 20, 2007 8:53:41 PM EST >To: ext Aaron Falk >Cc: , "mobopts@irtf.org" >Subject: IRSG review of draft-irtf-mobopts-l2-abstractions-04.txt >completed > > >Hi Aaron, > >This note is to formally request you to advance the MobOpts RG ID >"Unified >L2 Abstractions for L3-Driven fast Handover" [1] to IESG for their "no >circumvention" review prior to its publication as an Experimental RFC. > >The detailed IRSG review (of version 03) and subsequent acceptance (of >version 04) by John Levine are available at > >http://www1.ietf.org/mail-archive/web/mobopts/current/msg00873.html > >The above review and the IRSG poll input are documented at the tracker >http://www3.tools.ietf.org/group/irtf/trac (which is currently down >for me >to provide the exact ticket #) > >Since this document represents the consensus of the MobOpts RG, I >request >that the following IESG note (taken from [2]) be included: > >"This document is not an IETF Internet Standard. It represents >the consensus of the MobOpts Research Group of the Internet Research >Task Force. It may be considered for standardization by the >IETF in the future." > >The IRSG poll provided input [3] which could be incorporated as RFC >Editor >notes. > >Thanks, > >-Rajeev >-- >http://people.nokia.net/~rajeev > > > > >[1]: http://tools.ietf.org/id/draft-irtf-mobopts-l2- >abstractions-04.txt > >[2]: http://www.irtf.org/chairfiles/draft-irtf-rfcs-01.html#iesg-notes > >[3]: >> >>Vote: Ready to publish >> >>Short Review: >> >>The document is very easy to read and understand. I have worked >>in this >>area (though more focused on L3-L4 interaction than L3-L2) and I >>think it >>is a useful and needed contribution. >> >>The diagrams are clear and the appendices provide useful supporting >>material. >> >>The "Architectural Considerations" section is a good idea for a >>document >>like this, and building off the IAB document was also a great idea. >> >>I didn't quite buy the logic on number 5, and suggest a different >>explanation >>instead of: >>> [5] Proposals must demonstrate that effective congestion >>>control is >>> maintained. >>> >>> Since this mechanism is coupled to the IP layer, and not >>> directly to the transport layer, the proposed mechanism does >>> not directly affect congestion control. >> >>I think it would be more correct to say: >>Since the proposed inter-layer communications are local within a >>host, >>and not across a network, they don't directly raise congestion >>control >>concerns. The response of individual protocols to these >>notifications >>should ensure that effective congestion control is maintained, but >>those >>instantiations are outside the scope of this document. >> >>Grammar/Spelling: >> >>"utilize other layer's control" -> >>"utilize other layers' control" ? > > > ----- End forwarded message ----- From apache@ticket.ietf.org Mon Dec 10 14:57:22 2007 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id lBAMut6M004865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 10 Dec 2007 14:56:57 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1J1rYV-0007QP-6S for rfc-editor@rfc-editor.org; Mon, 10 Dec 2007 17:56:55 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98415 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Mon, 10 Dec 2007 17:56:55 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98415] AutoReply: Informational Independent Submission: draft-levis-provider-qos-agreement-04.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 4 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Informational Independent Submission: draft-levis-provider-qos-agreement-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98415] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98415] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-levis-provider-qos-agreement-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Five week timeout expires on 14 January 2007. Please note that we have included an additional week because of the coming holidays. Considerations of provider-to-provider agreements for Internet-scale QoS This memo analyzes provider-to-provider QoS agreements suitable for a global QoS-enabled Internet. It defines terminology relevant to inter-domain QoS models. It proposes a new concept denoted by Meta-QoS-Class (MQC). This concept could potentially drive and federate the way QoS inter-domain relationships are built between providers. It opens up new perspectives for a QoS-enabled Internet that retains, as much as possible, the openness of the existing best-effort Internet. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From apache@ticket.ietf.org Wed Jan 2 18:57:14 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032uEfh009033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:56:16 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGFi-0000eo-HQ for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:56:14 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98639 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:56:14 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98639] AutoReply: Re: Document Action: 'Session Initiation Protocol (SIP) Session Mobility' to Informational RFC Status: O X-Status: X-Keywords: $NotJunk X-UID: 5 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Document Action: 'Session Initiation Protocol (SIP) Session Mobility' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98639] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98639] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 04:27:41PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'Session Initiation Protocol (SIP) Session Mobility ' > as an Informational RFC > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Jon Peterson. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-shacham-sipping-session-mobility-05.txt > > Technical Summary > > This document specifies a method in which media flows can migrate between > SIP devices in order to enable session mobility. The Service Location > Protocol is employed to locate targets for session transfer. > > Working Group Summary > > This document is an individual submission, but the SIPPING working group > was an early venue for its discussion. > > Protocol Quality > > This document was reviewed for the IESG by Jon Peterson. Francis Dupont > was the Gen-ART reviewer. Pete McCann reviewed this document for the > Mobility Directorate. From apache@ticket.ietf.org Wed Jan 2 18:57:17 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032tnG8008820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:55:50 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGFI-0000eM-Pr for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:55:48 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98638 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:55:48 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98638] AutoReply: Re: Protocol Action: 'Revised Civic Location Format for PIDF-LO' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 6 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Protocol Action: 'Revised Civic Location Format for PIDF-LO' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98638] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98638] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 04:22:43PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'Revised Civic Location Format for PIDF-LO ' > as a Proposed Standard > > This document is the product of the Geographic Location/Privacy Working > Group. > > The IESG contact persons are Cullen Jennings. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-geopriv-revised-civic-lo-07.txt > > Technical Summary > > This document defines an XML format for the representation of civic > location. This format is designed for use with PIDF Location Object > (PIDF-LO) documents. The format is based on the civic address > definition in PIDF-LO, but adds several new elements based on the > civic types defined for DHCP, and adds a hierarchy to address complex > road identity schemes. The format also includes support for the > xml:lang language tag and restricts the types of elements where > appropriate. > > > Working Group Summary > > This document was reviewed by the GEOPRIV working group, where it > has reached consensus for publication as an IETF RFC. > > > Document Quality > > The XML Schema contained within this document has been checked > against Xerces-J 2.6.2. > > In addition to updating RFC 4119, this document is also a normative > reference in draft-ietf-ecrit-lost-05.txt. > > There are three known implementations of this specification. > > > Personnel > > The Document Shepherd is Robert Sparks. > The Responsible Area Director is Cullen Jennings. From apache@ticket.ietf.org Wed Jan 2 18:57:19 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032tjRI008778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:55:46 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGFF-0000e2-8Y for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:55:45 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98637 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:55:45 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98637] AutoReply: Re: Protocol Action: 'RTP payload format for Enhanced Variable Rate Wideband Codec (EVRC-WB) and media subtype updates for EVRC-B codec' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 7 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Protocol Action: 'RTP payload format for Enhanced Variable Rate Wideband Codec (EVRC-WB) and media subtype updates for EVRC-B codec' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98637] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98637] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 04:11:11PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'RTP payload format for Enhanced Variable Rate Wideband Codec > (EVRC-WB) and media subtype updates for EVRC-B codec ' > as a Proposed Standard > > This document is the product of the Audio/Video Transport Working Group. > > > The IESG contact persons is Cullen Jennings. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-evrc-wb-09.txt > > Technical Summary > > This document specifies real-time transport protocol (RTP) payload > formats to be used for the EVRC wideband codec (EVRC-WB) and updates the > media type registrations for EVRC-B codec (RFC 4788). Several media type > registrations are included for EVRC-WB RTP payload formats. In addition, a > file format is specified for transport of EVRC-WB speech data in storage > mode applications such as e-mail. > > > Working Group Summary > > The document has been reviewed by the AVT working group to ensure > consistency with RFC 4788 media type registration, and meets the necessary > requirements to for payload type specification. > > > Document Quality > > The draft has existing implementation and is required for 3GPP2. The > request for review of the media type in the ietf-type list was posted on > May 24, 2007. > > > Personnel > > Roni Even is the document shepherd. From apache@ticket.ietf.org Wed Jan 2 18:57:22 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032uH1n009065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:56:18 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGFl-0000ey-0d for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:56:17 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98640 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:56:17 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98640] AutoReply: Re: Document Action: 'Mobility Services Transport: Problem Statement' to Informational RFC Status: O X-Status: X-Keywords: $NotJunk X-UID: 8 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Document Action: 'Mobility Services Transport: Problem Statement' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98640] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98640] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 04:33:55PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'Mobility Services Transport: Problem Statement ' > as an Informational RFC > > This document is the product of the Mobility for IP: Performance, > Signaling and Handoff Optimization Working Group. > > The IESG contact persons are Jari Arkko and Mark Townsley. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mipshop-mis-ps-05.txt > > Technical Summary > > The document provides a problem statement for the exchange of > information to support handover in heterogeneous link environments. > This mobility support service allows more sophisticated handover > operations by making available information about network > characteristics, neighboring networks and associated characteristics, > indications that a handover should take place, and suggestions for > suitable target networks to which to handover. The mobility support > services work complementarily with IP mobility mechanisms to enhance > the overall performance and usability perception. > > Working Group Summary > > This is a product of the MIPSHOP WG. > > Protocol Quality > > The draft has been reviewed by numerous folks, including folks > who are proficient in transport and mobility. This document went > through a WG last call in the MIPSHOP WG. The document captures > the issues to be addressed in the MIPSHOP WG work for implementing > a transport for the IEEE 802.21 services. As such, the document > has also been reviewed by the IEEE 802.21 liaison and many of > their members. > > Jari Arkko has reviewed this specification for the IESG. Gorry > Fairhurst provided a transport review. > > Note to RFC Editor > > Remove annex and adding the following sentence in > Section 1: > > Requirements to support 802.21 by L3 and above transport are > described in [1] (work in progress). > > Please change in Section 5.2: > OLD: > A common security association negotiation method, independent > of any specific MSTP user, should be implemented. > NEW: > A common security association negotiation method, independent > of any specific MSTP user, should be implemented between the endpoints > > > > > of the MSTP. > > Please correct the following: On page 8: > /other standards bodies other than the IETF/ > ^^^^^ > - remove "other" > > On page 11 > /arrive at a rate of hundreds of milliseconds/ > - It should be "at an interval of hundreds of milliseconds". > > On page 11 > / to around 65000 bytes/ > ^^^^^^ > - Should be: to be normally less than 64KB, but may be greater than 64 > KB > > On page 15 > /TR2.The transport protocol shall be capable to support both IPv4 > and IPv6 versions/ > /TR2.The transport protocol shall be able to operate over both the IPv4 > and IPv6 network layer/ From apache@ticket.ietf.org Wed Jan 2 18:57:30 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032v7BJ009259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:57:08 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGGZ-0000fU-16 for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:57:07 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98641 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:57:07 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98641] AutoReply: Re: Document Action: 'A URN namespace for the Commission for the Management and Application of Geoscience Information (CGI)' to Informational RFC Status: O X-Status: X-Keywords: $Junk X-UID: 9 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Document Action: 'A URN namespace for the Commission for the Management and Application of Geoscience Information (CGI)' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98641] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98641] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 04:58:15PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'A URN namespace for the Commission for the Management and Application > of Geoscience Information (CGI) ' > as an Informational RFC > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Lisa Dusseault. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-sjdcox-cgi-urn-00.txt > > Technical Summary > > This document registers the "cgi" URN NID for the Commission for the > Management and Application of > Geoscience Information (CGI) for naming (i) persistent resources > published by the CGI, and (ii) resources published by organizations > that wish them to be used in the context of services conforming to > protocols and agreements issued by CGI. > > Working Group Summary > > Not a WG doc. > > Protocol Quality > > Lisa Dusseault reviewed this document for the IESG. From apache@ticket.ietf.org Wed Jan 2 18:57:33 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032vANt009274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:57:11 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGGb-0000fn-Bn for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:57:09 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98642 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:57:09 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98642] AutoReply: Re: Document Action: 'Service Selection for Mobile IPv6' to Informational RFC Status: O X-Status: X-Keywords: $Junk X-UID: 10 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Document Action: 'Service Selection for Mobile IPv6' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98642] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98642] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 04:35:40PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'Service Selection for Mobile IPv6 ' > as an Informational RFC > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Jari Arkko. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-korhonen-mip6-service-06.txt > > Technical Summary > > This document describes a Service Selection Mobility Option for both > conventional Mobile IPv6 and Proxy Mobile IPv6 that is intended to > assist home agents to make a specific service selection for the > mobility service subscription during the binding update procedure. > introduction. The service selection may affect home agent routing > decisions, Qos and policy treatment of service related IP flows in the > home agent and also Home Address or Home Network Prefix assignment > policies. > > Working Group Summary > > This document is an individual submission. The document was > presented in MIP6 WG meetings and interest raised especially > from Proxy Mobile IPv6 deployment scenarios. The document was > proposed to be a WG work item. However, the decision of adoption > as a WG work item got postponed due time schedule challenges > with the current MIP6 WG charter. > > Document Quality > > There are no publicly known implementations yet. There is certain > level of interest from 3GPP SAE work to adopt the document as a > part of their architecture. > > Jari Arkko has reviewed this specification for the IESG. Based > on the AD review, a revised document was submitted. From apache@ticket.ietf.org Wed Jan 2 18:57:36 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (stiedprtick1.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m032vBhw009282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jan 2008 18:57:13 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JAGGd-0000ft-EZ for rfc-editor@rfc-editor.org; Wed, 02 Jan 2008 21:57:11 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98643 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 02 Jan 2008 21:57:11 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98643] AutoReply: Re: Document Action: 'A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)' to Informational RFC Status: O X-Status: X-Keywords: $NotJunk X-UID: 11 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Document Action: 'A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98643] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98643] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Jan 02, 2008 at 05:00:17PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'A Uniform Resource Name (URN) Namespace for the International > Organization for Standardization (ISO) ' > as an Informational RFC > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Lisa Dusseault. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-goodwin-iso-urn-03.txt > > Technical Summary > > This document describes a Uniform Resource Name Namespace > Identification (URN NID) for the International Organization for > Standardization (ISO). This URN NID is intended for use for the > identification of persistent resources published by the ISO standards > body (including documents, document metadata, extracted resources > such as standard schemata and standard value sets, and other > resources).(What does this protocol do and why does the community need > it?) > > Working Group Summary > > This is the product of an individual submitter; it was reviewed on > urn-nid list as required, and no issues were found. > > Protocol Quality > > This document was reviewed by Ted Hardie and Lisa Dusseault for the IESG. > > Radia Perlman was the SecDir reviewer and Eric Gray was the GenArt > reviewer. Frank Ellerman reviewed the doc including the ABNF. > > Note to RFC Editor > > The proposed status is Informational -- please make sure the document > gets published as Informational as it says in the tracker, not as Proposed > Standard as it says in the document. From apache@ticket.ietf.org Fri Jan 11 16:03:05 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from ticket.ietf.org (ticket.ietf.ORG [156.154.16.147]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m0C026Il025863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 11 Jan 2008 16:02:08 -0800 (PST) Received: from apache by ticket.ietf.org with local (Exim 4.43) id 1JDTp8-00033Y-Gu for rfc-editor@rfc-editor.org; Fri, 11 Jan 2008 19:02:06 -0500 From: "IETF-IESG-Support via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #98764 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Fri, 11 Jan 2008 19:02:06 -0500 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: apache@ticket.ietf.org Subject: [Inquiry #98764] AutoReply: Re: Protocol Action: 'Hash Based Addresses (HBA)' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 12 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Re: Protocol Action: 'Hash Based Addresses (HBA)' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #98764] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #98764] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Fri, Jan 11, 2008 at 04:29:18PM -0500, The IESG wrote: > The IESG has approved the following document: > > - 'Hash Based Addresses (HBA) ' > as a Proposed Standard > > This document is the product of the Site Multihoming by IPv6 > Intermediation Working Group. > > The IESG contact persons are Jari Arkko and Mark Townsley. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-shim6-hba-05.txt > > Technical Summary > > Hash Based Addresses are intended to provide a secure binding > between the multiple addresses with different prefixes available > to a host within a multihomed site. Information about the > multiple prefixes is included within the addresses by generating > the interface identifiers of the addresses of a host as hashes of > the set of available prefixes and a random number, which are then > appended to the the different prefixes. The result is a set of > addresses that are inherently bound together such that given one > valid address out of the group, the prefix set and the random > number, it is possible to determine whether another address is > part of the group by computing the hash and checking against the > interface identifier value. > > Working Group Summary > > The document has extensively reviewed by the Working Group and by > the Security Area Directorate. The Working Group consensus was to > recommend publication of this document as a Proposed Standard. > > Protocol Quality > > Jari Arkko has reviewed this specification for the IESG. > > There are known implementations of this specification, and there > have been no implemtation experiences that have implied any > further revision to this specification is required. > > Note to RFC Editor > > Please add a new subsection: > > 11.x.DoS attacks considerations > > In order to use the HBA technique, the owner of the HBA set must inform > about the CGA Parameter Data Structure to its peer in order to allow the > peer to verify tat the different HBAs belong to the same HBA set. Such > information must then be stored by the peer to verify alternative > addresses in the future. This can be a vector for DoS attacks, since the > peer must commit resources (in this particular case memory) to be able to > use the HBA technique for address verification. It is then possible for an > attacker to launch a DoS attack by conveying HBA information to a victim, > imposing the victim to use memory for storing HBA related state, and > eventually running out of memory for other genuine operations. In order to > prevent such attack, protocols that use the HBA technique should implement > proper DoS prevention techniques. For instance, the Shim6 protocol > (draft-ietf-shim6-proto] includes a 4-way handshake to establish the Shim6 > context and in particular to establish the HBA-related state. In this > 4-way handshake, the receiver remains stateless during the first 2 > messages, while the initiator must keep state throughout the exchange of > the 4 messages, so that the cost of the context establishment is higher in > memory terms for the initiator (i.e. the potential attacker) than for the > receiver (i.e. the potential victim). In addition to that, the 4-way > handshake, prevents the usage of spoofed addresses from off-path attacker, > since the initiator must be able to receive information through the > address it has used as source address, enabling the tracking of the > location from which the attack was launched from. From root@core3.amsl.com Thu Feb 21 18:45:23 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.0 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m1M2iwc1012677 for ; Thu, 21 Feb 2008 18:44:59 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 0) id B1F923A6839; Thu, 21 Feb 2008 18:45:01 -0800 (PST) Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: rfc-editor@rfc-editor.org Cc: iesg@ietf.org From: IESG Secretary Message-Id: <20080222024501.B1F923A6839@core3.amsl.com> Date: Thu, 21 Feb 2008 18:45:01 -0800 (PST) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: root@core3.amsl.com Subject: Regarding draft-ietf-smime-symkeydist-10.txt Status: O X-Status: X-Keywords: $Junk X-UID: 13 Subject: draft-ietf-smime-symkeydist-10.txt This document has been in the RFC Editor queue since February 2003. It has been waiting on a normative dependency on draft-ietf-pkix-2797-bis. That document is finally close to publication -- just two more IESG DISCUSS positions to resolve. Some things have changed in the five years that this document has been waiting, so the author just posted an update to align the two documents. Considering the time that has passed, the changes are very few. Please accept this update, and treat these changes similar to Auth48 changes. The IESG has reviewed them, and they do not require further review. For more background information, please see the trail below: Date: Mon, 3 Dec 2007 11:48:35 -0800 From: RFC Editor To: IESG Cc: kfall@cs.berkeley.edu, RFC Editor Subject: RFC database: additional information regarding GRE RFC's IESG, We received this inquiry below about the relationships between some GRE RFCs. Do you have any input on whether RFC 1701 should be updated/obsoleted by RFC 2784? Thanks, Sandy ----- Forwarded message from Kevin Fall ----- To: rfc-editor@rfc-editor.org From: Kevin Fall Subject: RFC database: additional information regarding GRE RFC's Date: Sat, 17 Nov 2007 15:28:48 -0800 Hi. I was going through the RFC search tool and noticed that the Obsoletes/Updates field for some of the GRE-related RFCs appear to be missing. In particular, I would have expected 1701 to be listed as updated (obsoleted?) by 2784, which in turn is updated by 2890. Do I have this correct? thx, - Kevin ----- End forwarded message ----- At 12:18 PM 2/21/2008, Mark Townsley wrote: >Secretary, > >Please clarify to the RFC Editor that: > >RFC 2890 updates RFC 2784. Neither are an update of RFC 1701 or 1702. > >RFC 1702 is not supposed to be an update of 1701, it's supposed to >be an orthogonal and complementary document. > >Thank you, > >- Mark > From wwwrun@core3.amsl.com Mon Feb 25 13:55:49 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m1PLsH3b006191 for ; Mon, 25 Feb 2008 13:54:17 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id C881428CAE8; Mon, 25 Feb 2008 13:42:09 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080225212907.GE8375@isi.edu> References: <20080221223001.C680C3A6C66@core3.amsl.com> <20080225212907.GE8375@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #2483 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 25 Feb 2008 13:42:09 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #2483] AutoReply: Re: draft-ietf-smime-symkeydist-10.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 14 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: draft-ietf-smime-symkeydist-10.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #2483]. Please include the string: [rt.amsl.com #2483] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings IESG Secretariat, It looks like 2 messages got crossed here. We have updated our queue to reflect v10 for draft-ietf-smime-symkeydist-10.txt and we will use v10 as our starting point for publication. However, the message states "For more background information, please see the trail below:", but the mail messages below are about the relationship between RFCs 1701, 2784, and 2890. Could you please resend the messages (i.e., the one with the appropriate trail information for draft-ietf-smime-symkeydist-10.txt and the response to the relation between RFCs 1701, 2784, and 2890)? Thanks! Sandy On Thu, Feb 21, 2008 at 02:30:01PM -0800, The IESG wrote: > Subject: draft-ietf-smime-symkeydist-10.txt > > This document has been in the RFC Editor queue since February > 2003. It has been waiting on a normative dependency on > draft-ietf-pkix-2797-bis. That document is finally close to > publication -- just two more IESG DISCUSS positions to resolve. Some > things have changed in the five years that this document has been > waiting, so the author just posted an update to align the two > documents. Considering the time that has passed, the changes are > very few. Please accept this update, and treat these changes similar > to Auth48 changes. The IESG has reviewed them, and they do not > require further review. > > For more background information, please see the trail below: > > Date: Mon, 3 Dec 2007 11:48:35 -0800 > From: RFC Editor > To: IESG > Cc: kfall@cs.berkeley.edu, RFC Editor > Subject: RFC database: additional information regarding GRE RFC's > > IESG, > > We received this inquiry below about the relationships between some > GRE RFCs. Do you have any input on whether RFC 1701 should be > updated/obsoleted by RFC 2784? > > Thanks, > Sandy > > ----- Forwarded message from Kevin Fall ----- > > To: rfc-editor@rfc-editor.org > From: Kevin Fall > Subject: RFC database: additional information regarding GRE RFC's > Date: Sat, 17 Nov 2007 15:28:48 -0800 > > > Hi. > > I was going through the RFC search tool and noticed that the > Obsoletes/Updates field for some of the GRE-related RFCs appear to be > missing. > > In particular, I would have expected 1701 to be listed as updated > (obsoleted?) by 2784, which in turn is updated by 2890. Do I have > this correct? > > thx, > - Kevin > > ----- End forwarded message ----- > At 12:18 PM 2/21/2008, Mark Townsley wrote: > > >Secretary, > > > >Please clarify to the RFC Editor that: > > > >RFC 2890 updates RFC 2784. Neither are an update of RFC 1701 or 1702. > > > >RFC 1702 is not supposed to be an update of 1701, it's supposed to > >be an orthogonal and complementary document. > > > >Thank you, > > > >- Mark > > From wwwrun@core3.amsl.com Wed Feb 27 16:38:32 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m1S0Zbvo028044 for ; Wed, 27 Feb 2008 16:35:37 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 67D8E28C0E7; Wed, 27 Feb 2008 16:35:42 -0800 (PST) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #2483 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 27 Feb 2008 16:35:43 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #2483] Resolved: Re: draft-ietf-smime-symkeydist-10.txt Status: O X-Status: X-Keywords: $Junk X-UID: 15 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Feb 27 16:38:37 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m1S0Zb3x028043 for ; Wed, 27 Feb 2008 16:35:37 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 583123A6A1F; Wed, 27 Feb 2008 16:35:42 -0800 (PST) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080225212907.GE8375@isi.edu> References: <20080221223001.C680C3A6C66@core3.amsl.com> <20080225212907.GE8375@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #2483 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 27 Feb 2008 16:35:43 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #2483] Re: draft-ietf-smime-symkeydist-10.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 16 Hi Sandy, I believe we have unraveled the two messages from each other, and you should have received two revised messages today with both these issues as the IESG intended alert you to them. Please let us know if there are any other questions regarding either issue. Thank you! Amy On Mon Feb 25 13:42:09 2008, rfc-editor@rfc-editor.org wrote: > Greetings IESG Secretariat, > > It looks like 2 messages got crossed here. > > We have updated our queue to reflect v10 for > draft-ietf-smime-symkeydist-10.txt and we will use v10 as our starting > point for publication. However, the message states "For more > background information, please see the trail below:", but the mail > messages below are about the relationship between RFCs 1701, 2784, and > 2890. > > Could you please resend the messages (i.e., the one with the > appropriate trail information for draft-ietf-smime-symkeydist-10.txt > and the response to the relation between RFCs 1701, 2784, and 2890)? > > Thanks! > > Sandy > > > > On Thu, Feb 21, 2008 at 02:30:01PM -0800, The IESG wrote: > > Subject: draft-ietf-smime-symkeydist-10.txt > > > > This document has been in the RFC Editor queue since February > > 2003. It has been waiting on a normative dependency on > > draft-ietf-pkix-2797-bis. That document is finally close to > > publication -- just two more IESG DISCUSS positions to resolve. Some > > things have changed in the five years that this document has been > > waiting, so the author just posted an update to align the two > > documents. Considering the time that has passed, the changes are > > very few. Please accept this update, and treat these changes similar > > to Auth48 changes. The IESG has reviewed them, and they do not > > require further review. > > > > For more background information, please see the trail below: > > > > Date: Mon, 3 Dec 2007 11:48:35 -0800 > > From: RFC Editor > > To: IESG > > Cc: kfall@cs.berkeley.edu, RFC Editor > > Subject: RFC database: additional information regarding GRE RFC's > > > > IESG, > > > > We received this inquiry below about the relationships between some > > GRE RFCs. Do you have any input on whether RFC 1701 should be > > updated/obsoleted by RFC 2784? > > > > Thanks, > > Sandy > > > > ----- Forwarded message from Kevin Fall ----- > > > > To: rfc-editor@rfc-editor.org > > From: Kevin Fall > > Subject: RFC database: additional information regarding GRE RFC's > > Date: Sat, 17 Nov 2007 15:28:48 -0800 > > > > > > Hi. > > > > I was going through the RFC search tool and noticed that the > > Obsoletes/Updates field for some of the GRE-related RFCs appear to be > > missing. > > > > In particular, I would have expected 1701 to be listed as updated > > (obsoleted?) by 2784, which in turn is updated by 2890. Do I have > > this correct? > > > > thx, > > - Kevin > > > > ----- End forwarded message ----- > > At 12:18 PM 2/21/2008, Mark Townsley wrote: > > > > >Secretary, > > > > > >Please clarify to the RFC Editor that: > > > > > >RFC 2890 updates RFC 2784. Neither are an update of RFC 1701 or 1702. > > > > > >RFC 1702 is not supposed to be an update of 1701, it's supposed to > > >be an orthogonal and complementary document. > > > > > >Thank you, > > > > > >- Mark > > > > From wwwrun@core3.amsl.com Thu Mar 6 11:17:57 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m26JH1EZ027373 for ; Thu, 6 Mar 2008 11:17:01 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id BC8803A6A89; Thu, 6 Mar 2008 11:17:10 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080306191449.GA840@isi.edu> References: <469B63A4.7090407@cisco.com> <20080306191449.GA840@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #2944 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 06 Mar 2008 11:17:10 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #2944] AutoReply: Re: Approved under draft-irtf-rfcs-00 experiment: draft-irtf-hiprg-nat-04.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 17 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Approved under draft-irtf-rfcs-00 experiment: draft-irtf-hiprg-nat-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #2944]. Please include the string: [rt.amsl.com #2944] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Hi Mark and IESG Secretariat, We have been getting this document ready for publication (along with the rest of the HIP documents), but I realized that we never received the formal "no objection" message from the IESG Secretariat. The I-D tracker lists the state as "Approved-announcement to be sent". We can move this document to AUTH48, but we do not want to publish the document until we have received the notice from the IESG Secretariat. I don't know who has the token on this, but can one of you arrange for the announcement to be sent? Please let me know if there are any questions or problems. Thanks! Sandy On Mon, Jul 16, 2007 at 02:25:08PM +0200, Mark Townsley wrote: > > Dear Editor, > > draft-irtf-hiprg-nat-03.txt received an "RFC 3932 IESG Review" which did > result in a small update to the document and is reflected in version > -04. The current version is now "approved" (note the quotes) from the > perspective of the IESG. This was done according to the experimental > IRTF document handling process described in draft-irtf-rfcs-00.txt. > According to section 2.6, the IESG is supposed to identify the proper > disclaimer to be inserted in the document. That disclaimer should be: > > "This RFC is a product of the Internet Research Task Force and > is not a candidate for any level of Internet Standard. The > IRTF publishes the results of Internet-related research and > development activities. These results might not be suitable > for deployment." > > According to section 2.5 and 2.7 of draft-irtf-rfcs-00, the next step > now is to hand the document to the RFC Editor for handling as follows: > > 2.5. RFC Editor Handling > > The document is submitted to the RFC Editor who does not perform an > ISR review. The RFC Editor sends it to the IESG for an RFC3932 > review. There are several reasons why the IESG may block a document, > described in RFC3932 section 4. (The document shepherd should be > responsible for checking the IETF datatracker for IESG blocking and > non-blocking comments and forward them to the RG.) > > 2.7. Exiting > > The document enters the RFC Editor queue at the same priority as IETF > documents. The document shepherd is responsible for ensuring that > the document authors are responsive to the RFC Editor and that the > RFC editing process goes smoothly. > > Let me know if there is anything else you are expecting from me or the > IESG. > > Thanks, > > - Mark > > PS. This request was originally sent to the iesg-secretary to be > communicated, in turn, to the RFC Editor. This created some procedural > discussion which has not been fully hashed out and understood by all. > Suffice to say that this document need not be held up any longer > though, and that we will nail down the proper set of procedures > in due course of the completion of draft-irtf-rfcs-xx.txt > > From wwwrun@core3.amsl.com Fri Mar 21 11:54:52 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m2LIr2KS003778 for ; Fri, 21 Mar 2008 11:53:03 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E644928C32B; Fri, 21 Mar 2008 11:55:19 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080321185147.GB15166@isi.edu> References: <20080321185147.GB15166@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #5844 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 21 Mar 2008 11:55:19 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #5844] AutoReply: Informational Independent Submission: draft-sanjib-private-vlan-09.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 18 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-sanjib-private-vlan-09.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #5844]. Please include the string: [rt.amsl.com #5844] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-sanjib-private-vlan-09.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 18 April 2008. Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment This document describes a mechanism to achieve device isolation through the application of special Layer 2 forwarding constraints. Such mechanism allows end devices to share the same IP subnet while being Layer 2 isolated, which in turn allows network designers to employ larger subnets and so reduce the address management overhead. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Thu Mar 27 12:49:22 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m2RJlVP0022480 for ; Thu, 27 Mar 2008 12:47:32 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 5F0023A6AED; Thu, 27 Mar 2008 12:49:51 -0700 (PDT) Subject: Re: [rt.amsl.com #2944] AutoReply: Re: Approved under draft-irtf-rfcs-00 experiment: draft-irtf-hiprg-nat-04.txt From: "RFC Editor via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080327194532.GF19870@isi.edu> References: <469B63A4.7090407@cisco.com> <20080306191449.GA840@isi.edu> <20080327194532.GF19870@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #2944 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 27 Mar 2008 12:49:51 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Status: O X-Status: X-Keywords: $NotJunk X-UID: 19 Hi Mark, Just a reminder that we are moving toward the publication of a set of documents that are now in AUTH48. is one of the set. However, we have never received the offical "no problem with publication" message from the secretariat. (Please see emails below for more detail.) Could you please work with the secretariat to have the announcement sent? Or, let me know if there are any problems. Thanks! Sandy On Thu, Mar 06, 2008 at 11:17:10AM -0800, IETF-IESG via RT wrote: > > Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "Re: Approved under draft-irtf-rfcs-00 experiment: draft-irtf-hiprg-nat-04.txt", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has been > assigned an ID of [rt.amsl.com #2944]. > > Please include the string: > > [rt.amsl.com #2944] > > in the subject line of all future correspondence about this issue. To do so, > you may reply to this message. > > Thank you, > iesg-secretary@iesg.org > > ------------------------------------------------------------------------- > Hi Mark and IESG Secretariat, > > We have been getting this document ready for publication (along with > the rest of the HIP documents), but I realized that we never received > the formal "no objection" message from the IESG Secretariat. The I-D > tracker lists the state as "Approved-announcement to be sent". > > We can move this document to AUTH48, but we do not want to publish the > document until we have received the notice from the IESG Secretariat. > > I don't know who has the token on this, but can one of you arrange for > the announcement to be sent? > > Please let me know if there are any questions or problems. > > Thanks! > > Sandy > > > On Mon, Jul 16, 2007 at 02:25:08PM +0200, Mark Townsley wrote: > > > > Dear Editor, > > > > draft-irtf-hiprg-nat-03.txt received an "RFC 3932 IESG Review" which did > > result in a small update to the document and is reflected in version > > -04. The current version is now "approved" (note the quotes) from the > > perspective of the IESG. This was done according to the experimental > > IRTF document handling process described in draft-irtf-rfcs-00.txt. > > According to section 2.6, the IESG is supposed to identify the proper > > disclaimer to be inserted in the document. That disclaimer should be: > > > > "This RFC is a product of the Internet Research Task Force and > > is not a candidate for any level of Internet Standard. The > > IRTF publishes the results of Internet-related research and > > development activities. These results might not be suitable > > for deployment." > > > > According to section 2.5 and 2.7 of draft-irtf-rfcs-00, the next step > > now is to hand the document to the RFC Editor for handling as follows: > > > > 2.5. RFC Editor Handling > > > > The document is submitted to the RFC Editor who does not perform an > > ISR review. The RFC Editor sends it to the IESG for an RFC3932 > > review. There are several reasons why the IESG may block a document, > > described in RFC3932 section 4. (The document shepherd should be > > responsible for checking the IETF datatracker for IESG blocking and > > non-blocking comments and forward them to the RG.) > > > > 2.7. Exiting > > > > The document enters the RFC Editor queue at the same priority as IETF > > documents. The document shepherd is responsible for ensuring that > > the document authors are responsive to the RFC Editor and that the > > RFC editing process goes smoothly. > > > > Let me know if there is anything else you are expecting from me or the > > IESG. > > > > Thanks, > > > > - Mark > > > > PS. This request was originally sent to the iesg-secretary to be > > communicated, in turn, to the RFC Editor. This created some procedural > > discussion which has not been fully hashed out and understood by all. > > Suffice to say that this document need not be held up any longer > > though, and that we will nail down the proper set of procedures > > in due course of the completion of draft-irtf-rfcs-xx.txt > > > > > From wwwrun@core3.amsl.com Mon Apr 7 13:51:39 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m37Kmr2L001454 for ; Mon, 7 Apr 2008 13:48:54 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 3B1E928C3D4; Mon, 7 Apr 2008 13:48:34 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080407204722.GC16867@isi.edu> References: <20080407204722.GC16867@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6272 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 07 Apr 2008 13:48:34 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6272] AutoReply: Informational Independent Submission: draft-guy-iax-04.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 20 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-guy-iax-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6272]. Please include the string: [rt.amsl.com #6272] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-guy-iax-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 5 May 2008. IAX: Inter-Asterisk eXchange Version 2 This document describes IAX, the Inter-Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk PBX and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia. IAX is an "all in one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol. In addition, IAX uses a single UDP data stream on a static port greatly simplifying Network Address Translation (NAT) gateway traversal, eliminating the need for other protocols to work around NAT, and simplifying network and firewall management. IAX employs a compact encoding which decreases bandwidth usage and is well suited for Internet telephony service. In addition, its open nature permits new payload types additions needed to support additional services. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Mon Apr 7 13:51:44 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m37KnLZ2001701 for ; Mon, 7 Apr 2008 13:49:22 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D71E33A6B6C; Mon, 7 Apr 2008 13:49:06 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080407204722.GC16867@isi.edu> References: <20080407204722.GC16867@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6273 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 07 Apr 2008 13:49:06 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6273] AutoReply: Informational Independent Submission: draft-guy-iax-04.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 21 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-guy-iax-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6273]. Please include the string: [rt.amsl.com #6273] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-guy-iax-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 5 May 2008. IAX: Inter-Asterisk eXchange Version 2 This document describes IAX, the Inter-Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk PBX and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia. IAX is an "all in one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol. In addition, IAX uses a single UDP data stream on a static port greatly simplifying Network Address Translation (NAT) gateway traversal, eliminating the need for other protocols to work around NAT, and simplifying network and firewall management. IAX employs a compact encoding which decreases bandwidth usage and is well suited for Internet telephony service. In addition, its open nature permits new payload types additions needed to support additional services. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Tue Apr 8 11:56:50 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m38IsU3O012652 for ; Tue, 8 Apr 2008 11:54:31 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0454828C17F; Tue, 8 Apr 2008 11:54:13 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080408185151.GC22423@isi.edu> References: <20080321185147.GB15166@isi.edu> <20080408185151.GC22423@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6312 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 08 Apr 2008 11:54:13 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6312] AutoReply: Re: Informational Independent Submission: draft-sanjib-private-vlan-09.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 22 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Informational Independent Submission: draft-sanjib-private-vlan-09.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6312]. Please include the string: [rt.amsl.com #6312] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We are resending this message, as we note that the ID tracker lists this document as being in ID Exists. Thanks! RFC Editor On Fri, Mar 21, 2008 at 11:51:47AM -0700, RFC Editor wrote: > IESG, > > This RFC-to-be was submitted to the RFC Editor to be published as > Informational: draft-sanjib-private-vlan-09.txt. > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > Four week timeout expires on 18 April 2008. > > Cisco Systems' Private VLANs: > Scalable Security in a Multi-Client Environment > > This document describes a mechanism to achieve device isolation > through the application of special Layer 2 forwarding constraints. > Such mechanism allows end devices to share the same IP subnet while > being Layer 2 isolated, which in turn allows network designers to > employ larger subnets and so reduce the address management > overhead. > > > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents From wwwrun@core3.amsl.com Wed Apr 9 07:43:52 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m39EgeQu027855 for ; Wed, 9 Apr 2008 07:42:41 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 939A73A6D03; Wed, 9 Apr 2008 07:42:21 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #2944 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 09 Apr 2008 07:42:21 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #2944] Resolved: Re: Approved under draft-irtf-rfcs-00 experiment: draft-irtf-hiprg-nat-04.txt Status: O X-Status: X-Keywords: $Junk X-UID: 23 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 16 10:30:10 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3GHTHQ1005876 for ; Wed, 16 Apr 2008 10:29:18 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D47A428C4C1; Wed, 16 Apr 2008 10:28:40 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080416172748.GC13818@isi.edu> References: <20070213205056.GM7571@isi.edu> <20080416172748.GC13818@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6524 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 16 Apr 2008 10:28:40 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6524] AutoReply: Re: Experimental RFC to be: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 24 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Experimental RFC to be: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6524]. Please include the string: [rt.amsl.com #6524] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings All, Just a friendly reminder -- We do not believe we have received a response for this request for an RFC 3932 review. Please let us know the status of this document. Thank you. RFC Editor On Tue, Feb 13, 2007 at 12:50:56PM -0800, RFC Editor wrote: > IESG, > > This RFC-to-be was submitted to the RFC Editor to be published as > Experimental: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt. > > Following Brian's suggestion, this document is being submitted to the > IESG for early RFC 3932 review, since it contains a WG name in its > file name. > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > Four week timeout expires on 13 March 2007. > > > IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP) > > A tunnel broker with the Tunnel Setup Protocol (TSP) enables the > establishment of tunnels of various inner protocols, such as IPv6 > or IPv4, inside various outer protocols packets, such as IPv4, IPv6 > or UDP over IPv4 for IPv4 NAT traversal. The control protocol > (TSP) is used by the tunnel client to negotiate the tunnel with the > broker. A mobile node implementing TSP can be connected to both > IPv4 and IPv6 networks whether it is on IPv4 only, IPv4 behind a > NAT or on IPv6 only. A tunnel broker may terminate the tunnels on > remote tunnel servers or on itself. This document describes the > TSP protocol within the model of the tunnel broker model. > > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents > From wwwrun@core3.amsl.com Thu Apr 17 09:56:02 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3HGtFTO019833 for ; Thu, 17 Apr 2008 09:55:16 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 6CD973A6AD7; Thu, 17 Apr 2008 09:54:36 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6537 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org, townsley@cisco.com MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 17 Apr 2008 09:54:36 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6537] Resolved: Re: Experimental RFC to be: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt Status: O X-Status: X-Keywords: $Junk X-UID: 25 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Apr 29 17:42:37 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.0 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3U0fsJN028011 for ; Tue, 29 Apr 2008 17:41:55 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C306128C323; Tue, 29 Apr 2008 17:41:48 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080430004014.GC23710@isi.edu> References: <20080429145957.7C20A3A6CFA@core3.amsl.com> <20080430004014.GC23710@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6891 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 29 Apr 2008 17:41:48 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6891] AutoReply: Re: Protocol Action: 'Sieve Email Filtering: Environment Extension' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 26 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Sieve Email Filtering: Environment Extension' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6891]. Please include the string: [rt.amsl.com #6891] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Apr 29, 2008 at 07:59:57AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Sieve Email Filtering: Environment Extension ' > as a Proposed Standard > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Chris Newman. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-freed-sieve-environment-05.txt > > Technical Summary > > This document describes the "environment" extension to the Sieve > email filtering language. The "environment" extension gives a > Sieve script access to information about the Sieve interpreter > itself, where it is running, and about any transport connection > currently involved in transferring the message. > > > Working Group Summary > > This is an individual submission, but the document was extensively > reviewed on the Sieve WG mailing list. There was strong support > in favor of this document from implementors. There were some > discussions about list of initial attributes specified in the > document, but most of them were centered around naming. > > IETF Last Call Summary > > There was fairly extensive discussion during IETF last call > which resulted in several improvements to the document. It was > noted during last call that the extension has two different kinds > of environment information: static information about the evaluation > engine and dynamic information about remote IP/host. The community > felt it was not a problem to have one syntax cover both kinds of > environment data. > > Document Quality > > At least 5 people have reviewed the current or earlier versions > of the document. Posted comments were addressed in the latest > revision. There is 1 existing implementation and at least 3 > more are planned. > > Personnel > > Alexey Melnikov is the document shepherd. Chris Newman is the > responsible area director. > > Note to RFC Editor > > Abstract > OLD: > The "environment" extension gives Sieve access to information > about the environment where the Sieve interpreter is running. > NEW: > The "environment" extension gives a Sieve script access to > information about the Sieve interpreter itself, where it is > running, and about any transport connection currently involved > in transferring the message. From wwwrun@core3.amsl.com Tue Apr 29 18:04:33 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3U13uMG006609 for ; Tue, 29 Apr 2008 18:03:57 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id AC0823A6BFF; Tue, 29 Apr 2008 18:03:51 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080430010249.GD23710@isi.edu> References: <20080430010249.GD23710@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6892 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 29 Apr 2008 18:03:52 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6892] AutoReply: Experimental IRTF Submission: draft-irtf-dtnrg-ltp-09.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 27 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Experimental IRTF Submission: draft-irtf-dtnrg-ltp-09.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6892]. Please include the string: [rt.amsl.com #6892] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Experimental: draft-irtf-dtnrg-ltp-09.txt. This document is a product of the IRTF. The review history for this document can be found at: http://www3.tools.ietf.org/group/irtf/trac/ticket/21 Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 27 May 2008. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents ----- Forwarded message from Aaron Falk ----- Cc: Internet Research Steering Group , Kevin Fall From: Aaron Falk To: RFC Editor Subject: Request to publish 3 IRTF drafts: draft-irtf-dtnrg-{ltp, ltp-extensions, ltp-motivation} Date: Mon, 28 Apr 2008 19:47:59 -0700 Dear RFC Editor- Please publish the drafts: draft-irtf-dtnrg-ltp-09.txt draft-irtf-dtnrg-ltp-extensions-07.txt draft-irtf-dtnrg-ltp-motivation-06.txt as IRTF RFCs. The note below explains the review the drafts have undergone and the desired category to which they should be published. Kevin Fall (cc'ed) is to be the document shepherd for these drafts. Please be sure to copy him on communications with the authors. I believe it is desired that the documents be published together. Regards, --aaron falk IRTF Chair Begin forwarded message: >From: Kevin Fall >Date: April 28, 2008 7:34:05 PM PDT >To: Aaron Falk >Cc: Internet Research Steering Group , Delay Tolerant >Networking Interest List >Subject: Advancing the LTP documents > >Hi Aaron, IRSG, and DTNRG-- > >In accordance with current IRTF RFC processes, three of the >LTP-related documents [1-3] have now finished IRSG review >and are ready for you to send to the RFC editor. Documents [1-2] >are intended as Experimental RFCs, and document [3] is intended >as an Informational RFC. > >The respective tracker tickets [4-6] for these docs have links >to the various stages of the review. In particular, the >"Attachments" section in each ticket contains text files with >pointers to and/or specific review comments that came up >during either RG or IRSG review. > >Brief of discussion items by doc: > >[base]: > - concern about non-congestion-controlled LTP protocol > running atop UDP could be bad for the Internet. Document > now specifies LTP is designed for private links > > - LTP does not provide flow control. The consequence > of using lower-layer "link queues" is discussed in the > spec > > - LTP has "red" and "green" color segments that refer > to whether reliability is provided or not. There was > some confusion as to whether network-induced re-ordering > between red/green segments was a problem. [its not] > >[extensions]: > > - the extensions are really only security-related, so > the title now reflects this fact > >[motivation]: > > - some concern about the number of timers required, clarified > by a message on 2/7/07 as not being so huge > >I'll be shepherd for these documents. > >Regards, >Kevin. > >[1] http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-09.txt >[2] >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-extensions-07.txt >[3] >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-motivation-06.txt > >[4] http://www3.tools.ietf.org/group/irtf/trac/ticket/21 >[5] http://www3.tools.ietf.org/group/irtf/trac/ticket/22 >[6] http://www3.tools.ietf.org/group/irtf/trac/ticket/23 > ----- End forwarded message ----- From wwwrun@core3.amsl.com Tue Apr 29 18:08:03 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3U17AqV007719 for ; Tue, 29 Apr 2008 18:07:11 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 457ED3A6BAD; Tue, 29 Apr 2008 18:07:07 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080430010531.GE23710@isi.edu> References: <20080430010531.GE23710@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6893 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 29 Apr 2008 18:07:07 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6893] AutoReply: Experimental IRTF Submission: draft-irtf-dtnrg-ltp-extensions-07.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 28 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Experimental IRTF Submission: draft-irtf-dtnrg-ltp-extensions-07.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6893]. Please include the string: [rt.amsl.com #6893] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Experimental: draft-irtf-dtnrg-ltp-extensions-07.txt. This document is a product of the IRTF. The reviews for this document can be found at: http://www3.tools.ietf.org/group/irtf/trac/ticket/22 Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 27 May 2008. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents ----- Forwarded message from Aaron Falk ----- Cc: Internet Research Steering Group , Kevin Fall From: Aaron Falk To: RFC Editor Subject: Request to publish 3 IRTF drafts: draft-irtf-dtnrg-{ltp, ltp-extensions, ltp-motivation} Date: Mon, 28 Apr 2008 19:47:59 -0700 Dear RFC Editor- Please publish the drafts: draft-irtf-dtnrg-ltp-09.txt draft-irtf-dtnrg-ltp-extensions-07.txt draft-irtf-dtnrg-ltp-motivation-06.txt as IRTF RFCs. The note below explains the review the drafts have undergone and the desired category to which they should be published. Kevin Fall (cc'ed) is to be the document shepherd for these drafts. Please be sure to copy him on communications with the authors. I believe it is desired that the documents be published together. Regards, --aaron falk IRTF Chair Begin forwarded message: >From: Kevin Fall >Date: April 28, 2008 7:34:05 PM PDT >To: Aaron Falk >Cc: Internet Research Steering Group , Delay Tolerant >Networking Interest List >Subject: Advancing the LTP documents > >Hi Aaron, IRSG, and DTNRG-- > >In accordance with current IRTF RFC processes, three of the >LTP-related documents [1-3] have now finished IRSG review >and are ready for you to send to the RFC editor. Documents [1-2] >are intended as Experimental RFCs, and document [3] is intended >as an Informational RFC. > >The respective tracker tickets [4-6] for these docs have links >to the various stages of the review. In particular, the >"Attachments" section in each ticket contains text files with >pointers to and/or specific review comments that came up >during either RG or IRSG review. > >Brief of discussion items by doc: > >[base]: > - concern about non-congestion-controlled LTP protocol > running atop UDP could be bad for the Internet. Document > now specifies LTP is designed for private links > > - LTP does not provide flow control. The consequence > of using lower-layer "link queues" is discussed in the > spec > > - LTP has "red" and "green" color segments that refer > to whether reliability is provided or not. There was > some confusion as to whether network-induced re-ordering > between red/green segments was a problem. [its not] > >[extensions]: > > - the extensions are really only security-related, so > the title now reflects this fact > >[motivation]: > > - some concern about the number of timers required, clarified > by a message on 2/7/07 as not being so huge > >I'll be shepherd for these documents. > >Regards, >Kevin. > >[1] http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-09.txt >[2] >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-extensions-07.txt >[3] >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-motivation-06.txt > >[4] http://www3.tools.ietf.org/group/irtf/trac/ticket/21 >[5] http://www3.tools.ietf.org/group/irtf/trac/ticket/22 >[6] http://www3.tools.ietf.org/group/irtf/trac/ticket/23 > ----- End forwarded message ----- From wwwrun@core3.amsl.com Tue Apr 29 18:09:32 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3U18pOZ008649 for ; Tue, 29 Apr 2008 18:08:52 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 07BC03A6AFD; Tue, 29 Apr 2008 18:08:47 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080430010747.GF23710@isi.edu> References: <20080430010747.GF23710@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6894 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 29 Apr 2008 18:08:48 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6894] AutoReply: Informational IRTF Submission: draft-irtf-dtnrg-ltp-motivation-06.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 29 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational IRTF Submission: draft-irtf-dtnrg-ltp-motivation-06.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6894]. Please include the string: [rt.amsl.com #6894] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-irtf-dtnrg-ltp-motivation-06.txt. This document is a product of the IRTF. The reviews for this document can be found at: http://www3.tools.ietf.org/group/irtf/trac/ticket/23 Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 27 May 2008. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents ----- Forwarded message from Aaron Falk ----- Cc: Internet Research Steering Group , Kevin Fall From: Aaron Falk To: RFC Editor Subject: Request to publish 3 IRTF drafts: draft-irtf-dtnrg-{ltp, ltp-extensions, ltp-motivation} Date: Mon, 28 Apr 2008 19:47:59 -0700 Dear RFC Editor- Please publish the drafts: draft-irtf-dtnrg-ltp-09.txt draft-irtf-dtnrg-ltp-extensions-07.txt draft-irtf-dtnrg-ltp-motivation-06.txt as IRTF RFCs. The note below explains the review the drafts have undergone and the desired category to which they should be published. Kevin Fall (cc'ed) is to be the document shepherd for these drafts. Please be sure to copy him on communications with the authors. I believe it is desired that the documents be published together. Regards, --aaron falk IRTF Chair Begin forwarded message: >From: Kevin Fall >Date: April 28, 2008 7:34:05 PM PDT >To: Aaron Falk >Cc: Internet Research Steering Group , Delay Tolerant >Networking Interest List >Subject: Advancing the LTP documents > >Hi Aaron, IRSG, and DTNRG-- > >In accordance with current IRTF RFC processes, three of the >LTP-related documents [1-3] have now finished IRSG review >and are ready for you to send to the RFC editor. Documents [1-2] >are intended as Experimental RFCs, and document [3] is intended >as an Informational RFC. > >The respective tracker tickets [4-6] for these docs have links >to the various stages of the review. In particular, the >"Attachments" section in each ticket contains text files with >pointers to and/or specific review comments that came up >during either RG or IRSG review. > >Brief of discussion items by doc: > >[base]: > - concern about non-congestion-controlled LTP protocol > running atop UDP could be bad for the Internet. Document > now specifies LTP is designed for private links > > - LTP does not provide flow control. The consequence > of using lower-layer "link queues" is discussed in the > spec > > - LTP has "red" and "green" color segments that refer > to whether reliability is provided or not. There was > some confusion as to whether network-induced re-ordering > between red/green segments was a problem. [its not] > >[extensions]: > > - the extensions are really only security-related, so > the title now reflects this fact > >[motivation]: > > - some concern about the number of timers required, clarified > by a message on 2/7/07 as not being so huge > >I'll be shepherd for these documents. > >Regards, >Kevin. > >[1] http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-09.txt >[2] >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-extensions-07.txt >[3] >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ltp-motivation-06.txt > >[4] http://www3.tools.ietf.org/group/irtf/trac/ticket/21 >[5] http://www3.tools.ietf.org/group/irtf/trac/ticket/22 >[6] http://www3.tools.ietf.org/group/irtf/trac/ticket/23 > ----- End forwarded message ----- From wwwrun@core3.amsl.com Wed Apr 30 07:03:28 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.0 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3UE2jjM023427 for ; Wed, 30 Apr 2008 07:02:46 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 21F083A6E98; Wed, 30 Apr 2008 07:01:57 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6891 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 30 Apr 2008 07:01:58 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6891] Resolved: Re: Protocol Action: 'Sieve Email Filtering: Environment Extension' to Proposed Standard Status: O X-Status: X-Keywords: $Junk X-UID: 30 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 30 11:43:08 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3UIfb56008978 for ; Wed, 30 Apr 2008 11:41:38 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id F1E723A6BA4; Wed, 30 Apr 2008 11:41:18 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6893 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 30 Apr 2008 11:41:18 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6893] Resolved: Experimental IRTF Submission: draft-irtf-dtnrg-ltp-extensions-07.txt Status: O X-Status: X-Keywords: $Junk X-UID: 31 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 30 11:45:22 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3UIgrBD009572 for ; Wed, 30 Apr 2008 11:42:53 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D10F83A6BA4; Wed, 30 Apr 2008 11:42:49 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6894 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 30 Apr 2008 11:42:49 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6894] Resolved: Informational IRTF Submission: draft-irtf-dtnrg-ltp-motivation-06.txt Status: O X-Status: X-Keywords: $Junk X-UID: 32 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 30 11:45:52 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m3UIhPW1010153 for ; Wed, 30 Apr 2008 11:43:26 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 8B3F13A69C9; Wed, 30 Apr 2008 11:43:22 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6892 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 30 Apr 2008 11:43:22 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6892] Resolved: Experimental IRTF Submission: draft-irtf-dtnrg-ltp-09.txt Status: O X-Status: X-Keywords: $Junk X-UID: 33 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Fri May 2 12:35:17 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m42JX04c025842 for ; Fri, 2 May 2008 12:33:01 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 629AB28C24E; Fri, 2 May 2008 12:32:58 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080502193128.GB26096@isi.edu> References: <20080502193128.GB26096@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6988 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 02 May 2008 12:32:58 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6988] AutoReply: Informational Independent Submission: draft-santoni-timestampeddata-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 34 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-santoni-timestampeddata-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #6988]. Please include the string: [rt.amsl.com #6988] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-santoni-timestampeddata-03.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Syntax for binding documents with time stamps This document describes a syntax which can be used to bind a generic document (or any set of data, not necessarily protected by means of cryptographic techniques) to one or more time-stamp tokens obtained for that document, where "time-stamp token" has the meaning defined in RFC 3161. Additional types of temporal evidence are also supported. This document proposes a simple syntax based on the Cryptographic Message Syntax (RFC 3852). Four week timeout expires on 30 May 2008. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Fri May 2 15:26:37 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m42MPvmT001513 for ; Fri, 2 May 2008 15:25:58 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 01F383A69A2; Fri, 2 May 2008 15:25:54 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #6988 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 02 May 2008 15:25:54 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #6988] Resolved: Informational Independent Submission: draft-santoni-timestampeddata-03.txt Status: O X-Status: X-Keywords: $Junk X-UID: 35 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue May 6 15:28:25 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m46MRVVT011247 for ; Tue, 6 May 2008 15:27:32 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C601728C4B9; Tue, 6 May 2008 15:27:32 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080506222639.GF2488@isi.edu> References: <20080506222639.GF2488@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7210 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 06 May 2008 15:27:32 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7210] AutoReply: draft-templin-autoconf-dhcp-14.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 36 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "draft-templin-autoconf-dhcp-14.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7210]. Please include the string: [rt.amsl.com #7210] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, has been submitted to the RFC Editor for consideration for publication as an RFC. Please do not expire this draft. Thank you. RFC Editor From wwwrun@core3.amsl.com Tue May 6 15:46:16 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m46MjZpQ018917 for ; Tue, 6 May 2008 15:45:36 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 419953A689A; Tue, 6 May 2008 15:45:36 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7210 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 06 May 2008 15:45:37 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7210] Resolved: draft-templin-autoconf-dhcp-14.txt Status: O X-Status: X-Keywords: $Junk X-UID: 37 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed May 14 12:09:19 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4EJ7Fe9003486 for ; Wed, 14 May 2008 12:07:16 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id CAE813A6842; Wed, 14 May 2008 12:07:12 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080514190028.GE24579@isi.edu> References: <20080502193128.GB26096@isi.edu> <20080514190028.GE24579@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7337 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 14 May 2008 12:07:12 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7337] AutoReply: Re: Informational Independent Submission: draft-santoni-timestampeddata-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 38 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Informational Independent Submission: draft-santoni-timestampeddata-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7337]. Please include the string: [rt.amsl.com #7337] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, Please note that a problem has arisen with the OID registration for this draft, and until it is settled satisfactorily by the author, we wish to withdraw the draft from TO. We apologize for any confusion or inconvenience! Thanks, Sandy On Fri, May 02, 2008 at 12:31:28PM -0700, RFC Editor wrote: > IESG, > > This RFC-to-be was submitted to the RFC Editor to be published as > Informational: draft-santoni-timestampeddata-03.txt. > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > > Syntax for binding documents with time stamps > > This document describes a syntax which can be used to bind a generic > document (or any set of data, not necessarily protected by means of > cryptographic techniques) to one or more time-stamp tokens obtained > for that document, where "time-stamp token" has the meaning defined > in RFC 3161. Additional types of temporal evidence are also > supported. > > This document proposes a simple syntax based on the Cryptographic > Message Syntax (RFC 3852). > > > Four week timeout expires on 30 May 2008. > > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents From wwwrun@core3.amsl.com Tue May 20 20:42:08 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4L3eV0A010384 for ; Tue, 20 May 2008 20:40:32 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 95FBE3A6CA9; Tue, 20 May 2008 20:40:15 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080520163922.GB3818@isi.edu> References: <20080520163922.GB3818@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7431 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 20 May 2008 20:40:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7431] AutoReply: draft-bambenek-doubleflux-00.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 39 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "draft-bambenek-doubleflux-00.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7431]. Please include the string: [rt.amsl.com #7431] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, has been submitted to the RFC Editor for consideration for publication as an RFC. Please do not expire this draft. Thank you. RFC Editor From wwwrun@core3.amsl.com Wed May 21 09:08:55 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4LG7C5K013581 for ; Wed, 21 May 2008 09:07:13 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id EC4503A6979; Wed, 21 May 2008 09:07:07 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7431 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 21 May 2008 09:07:07 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7431] Resolved: draft-bambenek-doubleflux-00.txt Status: O X-Status: X-Keywords: $Junk X-UID: 40 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed May 21 09:18:50 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4LGEjvW017274 for ; Wed, 21 May 2008 09:14:45 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 08D7C28C1FF; Wed, 21 May 2008 09:14:39 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080521161354.GB20980@isi.edu> References: <20080521161354.GB20980@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7457 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 21 May 2008 09:14:40 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7457] AutoReply: Informational Independent Submission: draft-jcurran-v6transitionplan-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 41 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-jcurran-v6transitionplan-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7457]. Please include the string: [rt.amsl.com #7457] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-jcurran-v6transitionplan-03.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 18 June 2008. An Internet Transition Plan This memo provides one possible plan for transitioning the Internet from a predominantly IPv4-based connectivity model to a predominantly IPv6-based connectivity model. This document was reviewed by Bob Hinden. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Wed May 21 09:24:35 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4LGMMHC021215 for ; Wed, 21 May 2008 09:22:23 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 36FBA28C106; Wed, 21 May 2008 09:22:18 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080521162035.GC20980@isi.edu> References: <20080521162035.GC20980@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7459 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 21 May 2008 09:22:18 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7459] AutoReply: Informational Independent Submission: draft-floyd-tsvwg-besteffort-04.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 42 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-floyd-tsvwg-besteffort-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7459]. Please include the string: [rt.amsl.com #7459] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-floyd-tsvwg-besteffort-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 18 June 2008. Comments on the Usefulness of Simple Best-Effort Traffic This document presents some observations on "simple best-effort" traffic, defined loosely for the purposes of this document as Internet traffic that is not covered by Quality of Service mechanisms, congestion-based pricing, cost-based fairness, admissions control, or the like. One observation is that simple best-effort traffic serves a useful role in the Internet, and is worth keeping. While differential treatment of traffic can clearly be useful, we believe such mechanisms are useful as **adjuncts** to simple best-effort traffic, not as **replacements** of simple best-effort traffic. A second observation is that for simple best-effort traffic, some form of rough flow rate fairness is a useful goal for resource allocation, where "flow rate fairness" is defined by the goal of equal flow rates for different flows over the same path. This document was reviewed by Ted Faber. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Wed May 21 10:04:15 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4LH2qqV009519 for ; Wed, 21 May 2008 10:02:53 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 2FC323A6ACB; Wed, 21 May 2008 10:02:47 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7457 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 21 May 2008 10:02:47 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7457] Resolved: Informational Independent Submission: draft-jcurran-v6transitionplan-03.txt Status: O X-Status: X-Keywords: $Junk X-UID: 43 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu May 22 09:17:53 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4MGHA8o015062 for ; Thu, 22 May 2008 09:17:11 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E77CA3A6B02; Thu, 22 May 2008 09:17:09 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080522161631.GD13668@isi.edu> References: <20080522161631.GD13668@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7488 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 22 May 2008 09:17:09 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7488] AutoReply: draft-saleem-msml-06.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 44 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "draft-saleem-msml-06.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7488]. Please include the string: [rt.amsl.com #7488] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We believe that has mistakenly been allowed to expire. This document is under consideration for pubication with the RFC Editor. Please revive version -06 in the internet-drafts repository. Please let us know if this poses any problems or if you have any questions. Thank you. RFC Editor From wwwrun@core3.amsl.com Fri May 23 13:23:58 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4NKMdVK013080 for ; Fri, 23 May 2008 13:22:40 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id ABFF228C306; Fri, 23 May 2008 13:22:39 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7459 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 23 May 2008 13:22:39 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7459] Resolved: Informational Independent Submission: draft-floyd-tsvwg-besteffort-04.txt Status: O X-Status: X-Keywords: $Junk X-UID: 45 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu May 29 12:25:00 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4TJ1GKS016395 for ; Thu, 29 May 2008 12:01:16 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id EB6E53A6B87; Thu, 29 May 2008 12:00:41 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7488 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 29 May 2008 12:00:41 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7488] Resolved: draft-saleem-msml-06.txt Status: O X-Status: X-Keywords: $Junk X-UID: 46 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu May 29 12:25:02 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4TJ0vt0016084 for ; Thu, 29 May 2008 12:00:58 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 5F47D28C295; Thu, 29 May 2008 12:00:28 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080522161631.GD13668@isi.edu> References: <20080522161631.GD13668@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7488 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 29 May 2008 12:00:28 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7488] draft-saleem-msml-06.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 47 Dear RFC Editor, draft-saleem-msml's status is still in Active (not Expired) in the database; however, the draft's state in the I-D tracker is Dead because the IESG sent out a DNP notice on this draft. (In this case, "Status" and "State" refer to two different things.) The draft was marked as "Under Review by RFC Editor" in the database, so it should not expire in August 2008 as it was originally expected to. The draft itself is still active and accessible from the Internet Draft Database Interface at https://datatracker.ietf.org/drafts/draft-saleem-msml/ Best regards, Cindy On Thu May 22 09:17:09 2008, rfc-editor@rfc-editor.org wrote: > Greetings, > > We believe that has mistakenly been allowed > to expire. This document is under consideration for pubication with > the RFC Editor. Please revive version -06 in the internet-drafts > repository. > > Please let us know if this poses any problems or if you have any > questions. > > Thank you. > > RFC Editor > From wwwrun@core3.amsl.com Thu May 29 15:20:48 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4TMEX30001887 for ; Thu, 29 May 2008 15:14:34 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 917573A6BB6; Thu, 29 May 2008 15:14:33 -0700 (PDT) Subject: Re: [rt.amsl.com #7488] draft-saleem-msml-06.txt From: "RFC Editor via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080529220955.GF28433@isi.edu> References: <20080522161631.GD13668@isi.edu> <20080529220955.GF28433@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7488 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 29 May 2008 15:14:33 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Status: O X-Status: X-Keywords: $NotJunk X-UID: 48 Thanks for the clarification! Sandy On Thu, May 29, 2008 at 12:00:28PM -0700, Cindy Morgan via RT wrote: > Dear RFC Editor, > > draft-saleem-msml's status is still in Active (not Expired) in the > database; however, the draft's state in the I-D tracker is Dead because > the IESG sent out a DNP notice on this draft. (In this case, "Status" > and "State" refer to two different things.) > > The draft was marked as "Under Review by RFC Editor" in the database, so > it should not expire in August 2008 as it was originally expected to. > The draft itself is still active and accessible from the Internet Draft > Database Interface at https://datatracker.ietf.org/drafts/draft-saleem-msml/ > > Best regards, > Cindy > > > On Thu May 22 09:17:09 2008, rfc-editor@rfc-editor.org wrote: > > Greetings, > > > > We believe that has mistakenly been allowed > > to expire. This document is under consideration for pubication with > > the RFC Editor. Please revive version -06 in the internet-drafts > > repository. > > > > Please let us know if this poses any problems or if you have any > > questions. > > > > Thank you. > > > > RFC Editor > > > > From wwwrun@core3.amsl.com Thu May 29 16:27:54 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4TNOif5009899 for ; Thu, 29 May 2008 16:24:45 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 9643A3A6B5D; Thu, 29 May 2008 16:24:44 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7488 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 29 May 2008 16:24:44 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7488] Resolved: draft-saleem-msml-06.txt Status: O X-Status: X-Keywords: $Junk X-UID: 49 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Mon Jun 2 16:11:13 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m52NA9Fg008570 for ; Mon, 2 Jun 2008 16:10:13 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 1EECA28C17D; Mon, 2 Jun 2008 16:09:33 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080602230530.GE4939@isi.edu> References: <20080602230530.GE4939@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7750 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 02 Jun 2008 16:09:34 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7750] AutoReply: Informational Independent Submission: draft-ietf-ediint-compression-11.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 50 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-ietf-ediint-compression-11.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7750]. Please include the string: [rt.amsl.com #7750] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-ietf-ediint-compression-11.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 30 June 2008. Compressed Data within an Internet EDI Message This document explains the rules and procedures for utilizing compression (RFC 3274) within an Internet EDI (Electronic Data Interchange) 'AS' message, as defined in RFCs 3335, 4130, and 4823. This document was reviewed by the RFC Editor and by Jim Schaad, with additional input from Harald Alvestrand, and the document was updated to meet all reviewer recommendations. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Wed Jun 4 11:39:27 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m54Iccfh018875 for ; Wed, 4 Jun 2008 11:38:39 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 95E7A28C1F5; Wed, 4 Jun 2008 11:38:33 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7750 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 04 Jun 2008 11:38:33 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7750] Resolved: Informational Independent Submission: draft-ietf-ediint-compression-11.txt Status: O X-Status: X-Keywords: $Junk X-UID: 51 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu Jun 5 15:48:20 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m55MkWHX016617 for ; Thu, 5 Jun 2008 15:46:33 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id EB0733A6815; Thu, 5 Jun 2008 15:46:24 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080605224443.GE23686@isi.edu> References: <20080605224443.GE23686@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7813 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 05 Jun 2008 15:46:24 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7813] AutoReply: Informational Independent Submission: draft-munakata-sip-privacy-guideline-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 52 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-munakata-sip-privacy-guideline-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7813]. Please include the string: [rt.amsl.com #7813] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-munakata-sip-privacy-guideline-03.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 3 July 2008. Guidelines for Using the Privacy Mechanism for SIP This is an informational document that provides guidelines for using the privacy mechanism for Session Initiation Protocol (SIP), that is specified in RFC 3323 and subsequently extended in RFCs 3325 and 4244. It is intended to clarify the handling of the target SIP headers/parameters and SDP parameters for each of the privacy header values (priv-values). This document was reviewed by Mary Barnes and by Joel Halpern. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Fri Jun 6 10:18:29 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m56HI2xw008921 for ; Fri, 6 Jun 2008 10:18:03 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0C3CD3A6914; Fri, 6 Jun 2008 10:17:51 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7813 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 06 Jun 2008 10:17:52 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7813] Resolved: Informational Independent Submission: draft-munakata-sip-privacy-guideline-03.txt Status: O X-Status: X-Keywords: $Junk X-UID: 53 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Jun 10 19:11:29 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5B29jBP016288 for ; Tue, 10 Jun 2008 19:09:46 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 045753A6853; Tue, 10 Jun 2008 19:09:20 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080611020915.GE21895@isi.edu> References: <20080610130852.448FD3A6B66@core3.amsl.com> <20080611020915.GE21895@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7931 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 10 Jun 2008 19:09:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7931] AutoReply: Re: Protocol Action: 'Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 54 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7931]. Please include the string: [rt.amsl.com #7931] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Jun 10, 2008 at 06:08:52AM -0700, The IESG wrote: > The IESG has approved the following documents: > > - 'An Extensible Markup Language (XML) Patch Operations Framework > Utilizing XML Path Language (XPath) Selectors ' > as a Proposed Standard > - 'Presence Information Data format (PIDF) Extension for Partial > Presence ' > as a Proposed Standard > - 'Session Initiation Protocol (SIP) extension for Partial Notification > of Presence Information ' > as a Proposed Standard > - 'Publication of Partial Presence Information ' > as a Proposed Standard > > These documents are products of the SIP for Instant Messaging and > Presence Leveraging Extensions Working Group. > > The IESG contact persons are Jon Peterson and Cullen Jennings. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-simple-partial-notify-10.txt > > Technical Summary > > This document set provides a new capability for SIMPLE: partial > publications and notifications. Partial publications and notifications are > updates to previous transmitted presence documents which omit redundant > information, thereby saving bandwidth and processing. Both of these rely > on a common partial presence document format, 'application/pidf-diff+xml'. > These diffs are applied to existing presence documents through the > patching technique described in the xml-patch-ops document. > > Working Group Summary > > The working group supports the advancement of these specifications, and in > fact much protocol work inside and outside the IETF relies on this. > > Protocol Quality > > These documents were reviewed for the IESG by Jon Peterson. The PROTO > shepherd is Robert Sparks. Apps Area review of the XML-patch-ops document > was provided by Dave Crocker. Gen-ART review of XMLpatch-ops was provided > by Joel Halpern. From wwwrun@core3.amsl.com Tue Jun 10 19:20:53 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5B2JelU019481 for ; Tue, 10 Jun 2008 19:19:40 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id B187F3A68E6; Tue, 10 Jun 2008 19:19:15 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080611020940.GG21895@isi.edu> References: <20080610142506.118913A6937@core3.amsl.com> <20080611020940.GG21895@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7932 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 10 Jun 2008 19:19:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7932] AutoReply: Re: Document Action: 'Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)' to Informational RFC Status: O X-Status: X-Keywords: $NotJunk X-UID: 55 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Document Action: 'Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7932]. Please include the string: [rt.amsl.com #7932] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Jun 10, 2008 at 07:25:05AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge > (PWE3) ' > as an Informational RFC > > This document is the product of the Pseudowire Emulation Edge to Edge > Working Group. > > The IESG contact persons are Mark Townsley and Jari Arkko. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ms-pw-requirements-07.txt > > Technical Summary > > This document describes a protocol that provides a control channel > that is associated with a Pseudowire (PW), and its use for > operations and management functions such as connectivity > verification to be used over that control channel. VCCV > applies to all supported access circuit and transport types > currently defined for PWs. > > Working Group Summary > > This document has been reviewed by the experts in the PWE3 WG > and there are no outstanding issues. > > Document Quality > > The document was reviewed by Mark Townsley. Stewart Bryant is the > document shepherd. From wwwrun@core3.amsl.com Tue Jun 10 19:20:58 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5B2Jekj019482 for ; Tue, 10 Jun 2008 19:19:40 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id B803D3A68DD; Tue, 10 Jun 2008 19:19:15 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080611020928.GF21895@isi.edu> References: <20080610131059.81A423A6AC0@core3.amsl.com> <20080611020928.GF21895@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7933 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 10 Jun 2008 19:19:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7933] AutoReply: Re: Protocol Action: 'LoST: A Location-to-Service Translation Protocol' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 56 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'LoST: A Location-to-Service Translation Protocol' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7933]. Please include the string: [rt.amsl.com #7933] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Jun 10, 2008 at 06:10:59AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'LoST: A Location-to-Service Translation Protocol ' > as a Proposed Standard > > This document is the product of the Emergency Context Resolution with > Internet Technologies Working Group. > > The IESG contact persons are Jon Peterson and Cullen Jennings. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-10.txt > > Technical Summary > > This document describes an XML-based protocol for mapping service > identifiers and geodetic or civic location information to service > contact URIs. In particular, it can be used to determine the > location-appropriate PSAP for emergency services. > > Working Group Summary > > There is consensus in the WG to publish this document. > > Protocol Quality > > The LoST protocol has been implemented during the > development of the specification. Two public implementations > are available and other company-internal implementations > have been reported to the chairs. Tests have been performed > between two public implementations and useful feedback was > provided to the working group. > > The LoST specification has experienced extensive review, > including reviews by other SDOs. The protocol is an important > building block in the NENA i3 architecture. From wwwrun@core3.amsl.com Wed Jun 11 07:32:52 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5BEVTG9016207 for ; Wed, 11 Jun 2008 07:31:29 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 53AC73A690C; Wed, 11 Jun 2008 07:30:59 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7933 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 11 Jun 2008 07:30:59 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7933] Resolved: Re: Protocol Action: 'LoST: A Location-to-Service Translation Protocol' to Proposed Standard Status: O X-Status: X-Keywords: $Junk X-UID: 57 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Jun 11 07:33:08 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5BEWEuf016545 for ; Wed, 11 Jun 2008 07:32:15 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 9ABEA3A6936; Wed, 11 Jun 2008 07:31:48 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7932 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 11 Jun 2008 07:31:48 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7932] Resolved: Re: Document Action: 'Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)' to Informational RFC Status: O X-Status: X-Keywords: $Junk X-UID: 58 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Jun 11 07:34:18 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5BEX0Zc016932 for ; Wed, 11 Jun 2008 07:33:00 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 30FC83A690C; Wed, 11 Jun 2008 07:32:34 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7931 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 11 Jun 2008 07:32:34 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7931] Resolved: Re: Protocol Action: 'Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information' to Proposed Standard Status: O X-Status: X-Keywords: $Junk X-UID: 59 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Jun 11 13:09:31 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5BK85hU018900 for ; Wed, 11 Jun 2008 13:08:09 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 2A4143A689A; Wed, 11 Jun 2008 13:07:38 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080611200636.GC16340@isi.edu> References: <20080502193128.GB26096@isi.edu> <20080514190028.GE24579@isi.edu> <20080611200636.GC16340@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7956 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 11 Jun 2008 13:07:39 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7956] AutoReply: Re: Informational Independent Submission: draft-santoni-timestampeddata-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 60 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Informational Independent Submission: draft-santoni-timestampeddata-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #7956]. Please include the string: [rt.amsl.com #7956] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, We would like to restart the 4 week timeout for (note that the document has been updated to version -04). The OID registration has been resolved (by Russ Housley). This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-santoni-timestampeddata-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Syntax for binding documents with time stamps This document describes a syntax which can be used to bind a generic document (or any set of data, not necessarily protected by means of cryptographic techniques) to one or more time-stamp tokens obtained for that document, where "time-stamp token" has the meaning defined in RFC 3161. Additional types of temporal evidence are also supported. This document proposes a simple syntax based on the Cryptographic Message Syntax (RFC 3852). Four week timeout expires on 9 July 2008. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents On Wed, May 14, 2008 at 12:00:28PM -0700, RFC Editor wrote: > IESG, > > Please note that a problem has arisen with the OID registration for > this draft, and until it is settled satisfactorily by the author, we > wish to withdraw the draft from TO. > > We apologize for any confusion or inconvenience! > > Thanks, > Sandy > > > On Fri, May 02, 2008 at 12:31:28PM -0700, RFC Editor wrote: > > IESG, > > > > This RFC-to-be was submitted to the RFC Editor to be published as > > Informational: draft-santoni-timestampeddata-03.txt. > > > > Please let us know if this document conflicts with the IETF standards > > process or other work being done in the IETF community. > > > > > > Syntax for binding documents with time stamps > > > > This document describes a syntax which can be used to bind a generic > > document (or any set of data, not necessarily protected by means of > > cryptographic techniques) to one or more time-stamp tokens obtained > > for that document, where "time-stamp token" has the meaning defined > > in RFC 3161. Additional types of temporal evidence are also > > supported. > > > > This document proposes a simple syntax based on the Cryptographic > > Message Syntax (RFC 3852). > > > > > > Four week timeout expires on 30 May 2008. > > > > > > Sincerely, > > > > Sandy Ginoza - USC/ISI > > Request for Comments Documents From wwwrun@core3.amsl.com Wed Jun 11 14:36:38 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m5BLQnBv024425 for ; Wed, 11 Jun 2008 14:26:50 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 7063E3A6957; Wed, 11 Jun 2008 14:26:21 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #7956 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 11 Jun 2008 14:26:22 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #7956] Resolved: Re: Informational Independent Submission: draft-santoni-timestampeddata-03.txt Status: O X-Status: X-Keywords: $Junk X-UID: 61 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Jul 9 15:36:29 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m69MLBmv013530 for ; Wed, 9 Jul 2008 15:21:12 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id AC81E3A6860; Wed, 9 Jul 2008 15:20:57 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080709212043.GB22738@isi.edu> References: <20080709212043.GB22738@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #9195 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 09 Jul 2008 15:20:57 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #9195] AutoReply: Informational Independent Submission: draft-lochter-pkix-brainpool-ecc-01.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 62 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-lochter-pkix-brainpool-ecc-01.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #9195]. Please include the string: [rt.amsl.com #9195] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-lochter-pkix-brainpool-ecc-01.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Five week timeout expires on 13 August 2008. (Please note that we have included an additional week because of the upcoming IETF.) ECC Brainpool Standard Curves and Curve Generation This Memo proposes several elliptic curve domain parameters over finite prime fields for use in cryptographic applications. The domain parameters are consistent with the relevant international standards, and can be used in X.509 certificates and certificate revocation lists (CRLs), for Internet Key Exchange (IKE), Transport Layer Security (TLS), XML signatures, and all applications or protocols based on the cryptographic message syntax (CMS). This document was reviewed by Hal Finney, and his suggestion was incorporated in the -01 version. Finney wrote in review: "This is a very good idea. Present NIST curves do not have proofs that all their parameters are random, a fact which caused trouble when it came time to create the EC RNG in FIPS SP 800-90, as pointed out by Shumow and Ferguson, who found a possible backdoor. NIST curves also are optimized for performance, with field primes that have a lot of 1 bits at the top, allowing for very fast modular arithmetic. However certain techniques along these lines are patented so there is a risk that NIST may be inadvertently leading implementors into legal trouble. Using random primes will avoid this problem. Hopefully performance will still be acceptable.'This is a very good idea. Present NIST curves do not have proofs that all their parameters are random, a fact which caused trouble when it came time to create the EC RNG in FIPS SP 800-90, as pointed out by Shumow and Ferguson, who found a possible backdoor. NIST curves also are optimized for performance, with field primes that have a lot of 1 bits at the top, allowing for very fast modular arithmetic. However certain techniques along these lines are patented so there is a risk that NIST may be inadvertently leading implementors into legal trouble. Using random primes will avoid this problem. Hopefully performance will still be acceptable." Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Mon Jul 21 09:59:48 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m6LGx9hF021183 for ; Mon, 21 Jul 2008 09:59:10 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id EF1113A6ADD; Mon, 21 Jul 2008 09:58:29 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #9195 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 21 Jul 2008 09:58:29 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #9195] Resolved: Informational Independent Submission: draft-lochter-pkix-brainpool-ecc-01.txt Status: O X-Status: X-Keywords: $Junk X-UID: 63 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Jul 29 07:27:40 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m6TEQwWA000555 for ; Tue, 29 Jul 2008 07:26:59 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 1770028C1C2; Tue, 29 Jul 2008 07:26:45 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080729142606.GA2367@isi.edu> References: <20080729142606.GA2367@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #9798 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 29 Jul 2008 07:26:46 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #9798] AutoReply: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 64 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "draft-blanchet-v6ops-tunnelbroker-tsp-03.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #9798]. Please include the string: [rt.amsl.com #9798] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings! Can you please revive the following document: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt Thanks! RFC Editor From wwwrun@core3.amsl.com Tue Aug 5 12:10:47 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m75J9WsK027429 for ; Tue, 5 Aug 2008 12:09:33 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id A595228C314; Tue, 5 Aug 2008 12:09:00 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080805180825.GE18019@isi.edu> References: <20080709212043.GB22738@isi.edu> <20080805180825.GE18019@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #9934 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 05 Aug 2008 12:09:00 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #9934] AutoReply: Re: Informational Independent Submission: draft-lochter-pkix-brainpool-ecc-02.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 65 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Informational Independent Submission: draft-lochter-pkix-brainpool-ecc-02.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #9934]. Please include the string: [rt.amsl.com #9934] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, Please note that the author has posted a new version of this document. Please be sure to read draft-lochter-pkix-brainpool-ecc-02.txt during your review. Please let us know if you have any questions. Thank you. RFC Editor/sg On Wed, Jul 09, 2008 at 02:20:43PM -0700, RFC Editor wrote: > IESG, > > This RFC-to-be was submitted to the RFC Editor to be published as > Informational: draft-lochter-pkix-brainpool-ecc-01.txt. > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > Five week timeout expires on 13 August 2008. (Please note that we > have included an additional week because of the upcoming IETF.) > > ECC Brainpool Standard Curves and Curve Generation > > This Memo proposes several elliptic curve domain parameters over > finite prime fields for use in cryptographic applications. The > domain parameters are consistent with the relevant international > standards, and can be used in X.509 certificates and certificate > revocation lists (CRLs), for Internet Key Exchange (IKE), Transport > Layer Security (TLS), XML signatures, and all applications or > protocols based on the cryptographic message syntax (CMS). > > > This document was reviewed by Hal Finney, and his suggestion > was incorporated in the -01 version. Finney wrote in review: > > "This is a very good idea. Present NIST curves do not have proofs that > all their parameters are random, a fact which caused trouble when it > came time to create the EC RNG in FIPS SP 800-90, as pointed out by > Shumow and Ferguson, who found a possible backdoor. NIST curves also > are optimized for performance, with field primes that have a lot of 1 > bits at the top, allowing for very fast modular arithmetic. However > certain techniques along these lines are patented so there is a risk > that NIST may be inadvertently leading implementors into legal trouble. > Using random primes will avoid this problem. Hopefully performance will > still be acceptable.'This is a very good idea. Present NIST curves do > not have proofs that all their parameters are random, a fact which > caused trouble when it came time to create the EC RNG in FIPS SP > 800-90, as pointed out by Shumow and Ferguson, who found a possible > backdoor. NIST curves also are optimized for performance, with field > primes that have a lot of 1 bits at the top, allowing for very fast > modular arithmetic. However certain techniques along these lines are > patented so there is a risk that NIST may be inadvertently leading > implementors into legal trouble. Using random primes will avoid this > problem. Hopefully performance will still be acceptable." > > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents From wwwrun@core3.amsl.com Wed Aug 13 09:32:22 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7DGVHg0019503 for ; Wed, 13 Aug 2008 09:31:18 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 7E2C228C0D7; Wed, 13 Aug 2008 09:31:12 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080813162851.GA5935@isi.edu> References: <20080813162851.GA5935@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10052 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 13 Aug 2008 09:31:12 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10052] AutoReply: Informational IRTF Submission: draft-irtf-nmrg-snmp-measure-05.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 66 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational IRTF Submission: draft-irtf-nmrg-snmp-measure-05.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10052]. Please include the string: [rt.amsl.com #10052] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This IRTF RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-irtf-nmrg-snmp-measure-05.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 10 September 2008. SNMP Traffic Measurements and Trace Exchange Formats The Simple Network Management Protocol (SNMP) is widely deployed to monitor, control and (sometimes also) configure network elements. Even though the SNMP technology is well documented, it remains relatively unclear how SNMP is used in practice and what typical SNMP usage patterns are. This document describes an approach to carrying out large scale SNMP traffic measurements in order to develop a better understanding how SNMP is used in real world production networks. It describes the motivation, the measurement approach, and the tools and data formats needed to carry out such a study. This document was produced within the IRTF's Network Management Research Group (NMRG) and represents the consensus of all of the active contributors to this group. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents ----- Forwarded message from Aaron Falk ----- Cc: Internet Research Steering Group , Bert Wijnen From: Aaron Falk To: RFC Editor Subject: Request to publish draft-irtf-nmrg-snmp-measure-05 as Informational RFC Date: Thu, 31 Jul 2008 14:49:56 +0100 Dear RFC Editor- Please publish the above-named document as an Informational RFC from the IRTF. See below for more information. Bert Wijnen is the shepherd, please be sure to copy him on any correspondence related to this document (in addition to the authors, of course). --aaron Begin forwarded message: >From: "Bert Wijnen \(IETF\)" >Date: July 31, 2008 2:33:39 PM BST >To: "Aaron Falk" >Cc: "IRSG" >Subject: Request to publish draft-irtf-nmrg-snmp-measure-05 as >Informational RFC > >Arron, this is a request to publish this document as an >Informational RFC. > >The NMRG has gone through a number of review stages. Also individuals >who are know to be active in this space have been approached for >review. >This is all recorded in the issue tracker under ticket #9, see: > > http://www3.tools.ietf.org/group/irtf/trac/ticket/9 > >Summary of review: > - 15 reviews were recieved on this document during NMRG review >period. > this led to explanation from the author and to a few revisions to > include the required changes/clarifications. > - Each revision was posted and the NMRG has had time to review and > further comment. > - OPS AREA Director Dan Romascanu did issue an IETF Last Call on > revision 3 of this document because it DOES ask for a URI >registration > by IANA. No objections/comments were received. > - revision 4 was also reviewed by Karin R. Sollins which led to one >more > revision, the final revision (05) > - The final revision (05) was reviewed by the IRSG members > Karin R. Sollins and Stephen Farrell; They both voted YES on >the IRSG Poll for this revision. No objections were received. > >I have updated the status to: IRSG review concluded. > >Let me know if I need to do anything else. > >Bert Wijnen >Document Shepherd > ----- End forwarded message ----- From wwwrun@core3.amsl.com Wed Aug 13 09:34:03 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7DGXDoL020282 for ; Wed, 13 Aug 2008 09:33:14 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 11C1528C0EE; Wed, 13 Aug 2008 09:33:08 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080813162851.GA5935@isi.edu> References: <20080813162851.GA5935@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10053 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 13 Aug 2008 09:33:09 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10053] AutoReply: Informational IRTF Submission: draft-irtf-nmrg-snmp-measure-05.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 67 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational IRTF Submission: draft-irtf-nmrg-snmp-measure-05.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10053]. Please include the string: [rt.amsl.com #10053] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This IRTF RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-irtf-nmrg-snmp-measure-05.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 10 September 2008. SNMP Traffic Measurements and Trace Exchange Formats The Simple Network Management Protocol (SNMP) is widely deployed to monitor, control and (sometimes also) configure network elements. Even though the SNMP technology is well documented, it remains relatively unclear how SNMP is used in practice and what typical SNMP usage patterns are. This document describes an approach to carrying out large scale SNMP traffic measurements in order to develop a better understanding how SNMP is used in real world production networks. It describes the motivation, the measurement approach, and the tools and data formats needed to carry out such a study. This document was produced within the IRTF's Network Management Research Group (NMRG) and represents the consensus of all of the active contributors to this group. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents ----- Forwarded message from Aaron Falk ----- Cc: Internet Research Steering Group , Bert Wijnen From: Aaron Falk To: RFC Editor Subject: Request to publish draft-irtf-nmrg-snmp-measure-05 as Informational RFC Date: Thu, 31 Jul 2008 14:49:56 +0100 Dear RFC Editor- Please publish the above-named document as an Informational RFC from the IRTF. See below for more information. Bert Wijnen is the shepherd, please be sure to copy him on any correspondence related to this document (in addition to the authors, of course). --aaron Begin forwarded message: >From: "Bert Wijnen \(IETF\)" >Date: July 31, 2008 2:33:39 PM BST >To: "Aaron Falk" >Cc: "IRSG" >Subject: Request to publish draft-irtf-nmrg-snmp-measure-05 as >Informational RFC > >Arron, this is a request to publish this document as an >Informational RFC. > >The NMRG has gone through a number of review stages. Also individuals >who are know to be active in this space have been approached for >review. >This is all recorded in the issue tracker under ticket #9, see: > > http://www3.tools.ietf.org/group/irtf/trac/ticket/9 > >Summary of review: > - 15 reviews were recieved on this document during NMRG review >period. > this led to explanation from the author and to a few revisions to > include the required changes/clarifications. > - Each revision was posted and the NMRG has had time to review and > further comment. > - OPS AREA Director Dan Romascanu did issue an IETF Last Call on > revision 3 of this document because it DOES ask for a URI >registration > by IANA. No objections/comments were received. > - revision 4 was also reviewed by Karin R. Sollins which led to one >more > revision, the final revision (05) > - The final revision (05) was reviewed by the IRSG members > Karin R. Sollins and Stephen Farrell; They both voted YES on >the IRSG Poll for this revision. No objections were received. > >I have updated the status to: IRSG review concluded. > >Let me know if I need to do anything else. > >Bert Wijnen >Document Shepherd > ----- End forwarded message ----- From wwwrun@core3.amsl.com Wed Aug 13 10:47:36 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7DHkoBd022042 for ; Wed, 13 Aug 2008 10:46:51 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id ABC233A6A9C; Wed, 13 Aug 2008 10:46:39 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10053 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 13 Aug 2008 10:46:39 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10053] Resolved: Informational IRTF Submission: draft-irtf-nmrg-snmp-measure-05.txt Status: O X-Status: X-Keywords: $Junk X-UID: 68 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From root@core3.amsl.com Mon Aug 18 10:45:47 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.0 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7IHjKvs028977 for ; Mon, 18 Aug 2008 10:45:21 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 0) id 504E83A67DB; Mon, 18 Aug 2008 10:45:01 -0700 (PDT) From: IESG Secretary To: rfc-editor@rfc-editor.org Cc: iesg@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20080818174512.504E83A67DB@core3.amsl.com> Date: Mon, 18 Aug 2008 10:45:02 -0700 (PDT) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: root@core3.amsl.com Subject: RFC 3032 updated by RFCs 3270 and 5129 Status: O X-Status: X-Keywords: $Junk X-UID: 69 To: RFC Editor The IESG approved marking RFC 3032 as being updated by RFCs 3270 and 5129 (and vice versa). Best regards, IESG Secretary From wwwrun@core3.amsl.com Tue Aug 19 09:45:15 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7JGhLBx015965 for ; Tue, 19 Aug 2008 09:43:22 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id A5E923A68B2; Tue, 19 Aug 2008 09:43:12 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #9798 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 19 Aug 2008 09:43:12 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #9798] Resolved: draft-blanchet-v6ops-tunnelbroker-tsp-03.txt Status: O X-Status: X-Keywords: $Junk X-UID: 70 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Aug 26 12:10:57 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QJ9C4G015693 for ; Tue, 26 Aug 2008 12:09:13 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 125CD3A69F3; Tue, 26 Aug 2008 12:09:10 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080826190734.GC13193@isi.edu> References: <20080826190734.GC13193@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10228 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 12:09:10 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10228] AutoReply: Informational Independent Submission: draft-templin-autoconf-dhcp-16.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 71 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-templin-autoconf-dhcp-16.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10228]. Please include the string: [rt.amsl.com #10228] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Informational: draft-templin-autoconf-dhcp-16.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 23 September 2008. MANET Autoconfiguration using Virtual Enterprise Traversal (VET) Mobile Ad-hoc Networks (MANETs) connect routers on links with asymmetric reachability characteristics, and may also connect to other networks including the Internet. Routers in MANETs must have a way to automatically provision IP addresses/prefixes and other information. This document specifies a Virtual Enterprise Traversal (VET) abstraction for autoconfiguration and operation of routers in MANETs. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Tue Aug 26 12:15:29 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QJCaPx017731 for ; Tue, 26 Aug 2008 12:12:37 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 3E6173A6BEB; Tue, 26 Aug 2008 12:12:34 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080826190931.GD13193@isi.edu> References: <20080826190931.GD13193@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10229 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 12:12:34 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10229] AutoReply: Experimental Independent Submission: draft-templin-seal-23.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 72 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Experimental Independent Submission: draft-templin-seal-23.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10229]. Please include the string: [rt.amsl.com #10229] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Experimental: draft-templin-seal-23.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 23 September 2008. The Subnetwork Encapsulation and Adaptation Layer (SEAL) For the purpose of this document, subnetworks are defined as virtual topologies that span connected network regions bounded by encapsulated border nodes. These virtual topologies may span multiple IP- and/or sub-IP layer forwarding hops, and can introduce failure modes due to packet duplication and/or links with diverse Maximum Transmission Units (MTUs). This document specifies a Subnetwork Encapsulation and Adaptation Layer (SEAL) that accommodates such virtual topologies over diverse underlying link technologies. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Tue Aug 26 12:22:18 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QJL5C5023227 for ; Tue, 26 Aug 2008 12:21:06 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 3E8423A6BFC; Tue, 26 Aug 2008 12:21:03 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080826191311.GE13193@isi.edu> References: <20080826191311.GE13193@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10230 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 12:21:03 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10230] AutoReply: Experimental Independent Submission: draft-hajjeh-tls-identity-protection-05.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 73 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Experimental Independent Submission: draft-hajjeh-tls-identity-protection-05.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10230]. Please include the string: [rt.amsl.com #10230] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This RFC-to-be was submitted to the RFC Editor to be published as Experimental: draft-hajjeh-tls-identity-protection-05.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 23 September 2008. Credential Protection Ciphersuites for Transport Layer Security (TLS) The Transport Layer Security (TLS) supports three authentication modes: authentication of both parties, server authentication with an unauthenticated client, and total anonymity. For each mode, TLS specifies a set of cipher suites. Whenever the server is authenticated, the channel is secure against man-in-the-middle attacks, but completely anonymous sessions are inherently vulnerable to such attacks. The authentication is usually based on either preshared keys or public key certificates. If a public key certificate is used to authenticate the TLS client during the TLS Handshake, the TLS client credentials are sent in clear text over the wire. Thus, any observer can determine the credentials used by the client, learn who is reaching the network, when, and from where, and hence correlate the client credentials to the connection location. This document defines a set of cipher suites to add client credential protection to the TLS protocol. This is useful especially if TLS is used in wireless environments or to secure remote access. By negotiating one of the ciphersuites described in this document, the TLS clients will be able to determine for themselves when, how, to what extent and for what purpose information about them is communicated to others. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Tue Aug 26 13:23:58 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QKLOmo029836 for ; Tue, 26 Aug 2008 13:21:25 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E210D28C252; Tue, 26 Aug 2008 13:21:21 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10228 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 13:21:21 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10228] Resolved: Informational Independent Submission: draft-templin-autoconf-dhcp-16.txt Status: O X-Status: X-Keywords: $Junk X-UID: 74 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Aug 26 13:25:45 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QKNven001276 for ; Tue, 26 Aug 2008 13:23:58 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 520323A6C07; Tue, 26 Aug 2008 13:23:54 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10229 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 13:23:55 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10229] Resolved: Experimental Independent Submission: draft-templin-seal-23.txt Status: O X-Status: X-Keywords: $Junk X-UID: 75 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Aug 26 13:31:22 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QKTlLg004677 for ; Tue, 26 Aug 2008 13:29:48 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 7F46B3A6C0B; Tue, 26 Aug 2008 13:29:45 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10230 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 13:29:45 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10230] Resolved: Experimental Independent Submission: draft-hajjeh-tls-identity-protection-05.txt Status: O X-Status: X-Keywords: $Junk X-UID: 76 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Aug 26 16:58:02 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7QNvQd0006134 for ; Tue, 26 Aug 2008 16:57:27 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id B380F3A6C4D; Tue, 26 Aug 2008 16:57:22 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080826235547.GF13193@isi.edu> References: <20080826190931.GD13193@isi.edu> <3525C9833C09ED418C6FD6CD9514668C048BEAF2@emailwf1.jnpr.net> <20080826235547.GF13193@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10234 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 Aug 2008 16:57:22 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10234] AutoReply: Re: Experimental Independent Submission: draft-templin-seal-23.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 77 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Experimental Independent Submission: draft-templin-seal-23.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10234]. Please include the string: [rt.amsl.com #10234] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Hi Ross, This works for the RFC Editor. Thanks for keeping us informed! Sandy On Tue, Aug 26, 2008 at 07:44:09PM -0400, Ross Callon wrote: > I would like one additional week to consider this, so that I can put it > onto the IESG agenda for September 25, and reply to the RFC editor by > September 30th. > > Is this okay? > > Thanks, Ross > > -----Original Message----- > From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of > RFC Editor > Sent: 26 August 2008 15:10 > To: IESG; iesg-secretary > Cc: fltemplin@acm.org; RFC Editor > Subject: Experimental Independent Submission: draft-templin-seal-23.txt > > IESG, > > This RFC-to-be was submitted to the RFC Editor to be published as > Experimental: draft-templin-seal-23.txt > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > Four week timeout expires on 23 September 2008. > > > The Subnetwork Encapsulation and Adaptation Layer (SEAL) > > For the purpose of this document, subnetworks are defined as > virtual topologies that span connected network regions bounded by > encapsulated border nodes. These virtual topologies may span > multiple IP- and/or sub-IP layer forwarding hops, and can introduce > failure modes due to packet duplication and/or links with diverse > Maximum Transmission Units (MTUs). This document specifies a > Subnetwork Encapsulation and Adaptation Layer (SEAL) that > accommodates such virtual topologies over diverse underlying link > technologies. > > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents From wwwrun@core3.amsl.com Fri Aug 29 11:55:35 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7TIsIou029716 for ; Fri, 29 Aug 2008 11:54:19 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 7096428C113; Fri, 29 Aug 2008 11:54:14 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080829185242.GA21874@isi.edu> References: <20080829185242.GA21874@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10289 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 29 Aug 2008 11:54:14 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10289] AutoReply: Resubmit -- Informational Independent Submission: draft-saleem-msml-07.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 78 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Resubmit -- Informational Independent Submission: draft-saleem-msml-07.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10289]. Please include the string: [rt.amsl.com #10289] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-saleem-msml-07.txt. Please note that the IESG has previously requested a 6-month delay in publication (see email below): 3. The IESG thinks that publication is harmful to the IETF work done in the MEDIACTRL WG and recommends not publishing the document at this time. The MEDIACTRL chairs feel that this work directly competes with ongoing work in their group. We are resubmitting this document for an RFC 3932 IESG review. Four week timeout expires on 26 September 2008. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents On Mon, Sep 24, 2007 at 08:29:11PM -0400, The IESG wrote: > The IESG recommends that 'Media Server Markup Language (MSML)' > NOT be published as an an Informational RFC. > > The IESG contact person is Jon Peterson. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-saleem-msml-05.txt > > > The process for such documents is described at http://www.rfc-editor.org/indsubs.html. > > Thank you, > > The IESG Secretary > > Technical Summary > > This specification describes the Media Server Markup Language (MSML), a > language used to control and invoke a variety of services on media servers > used to support real-time communications. Common examples would be > conference services for audio and/or video bridges and interactive voice > response (IVR) systems. > > Working Group Summary > > This document is not a product of an IETF working group; it is an > individual submission via the RFC-Editor. > > Protocol Quality > > Jon Peterson performed the RFC3932 review of this document in conjunction > with the chairs of the MEDIACTRL working group. > > Note to RFC Editor > > Please use the following standard IESG note: > > This RFC is not a candidate for any level of Internet Standard. > The IETF disclaims any knowledge of the fitness of this RFC for > any purpose and in particular notes that the decision to publish > is not based on IETF review for such things as security, > congestion control, or inappropriate interaction with deployed > protocols. The RFC Editor has chosen to publish this document at > its discretion. Readers of this document should exercise caution > in evaluating its value for implementation and deployment. See > RFC 3932 for more information. > > IESG Note > > The IESG recommends the following: > > 3. The IESG thinks that publication is harmful to the IETF work done > in the MEDIACTRL WG and recommends not publishing the document at > this time. > > The MEDIACTRL chairs feel that this work directly competes with ongoing > work in their group. From wwwrun@core3.amsl.com Fri Aug 29 14:10:18 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7TL9MAE026599 for ; Fri, 29 Aug 2008 14:09:23 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 6C69228C151; Fri, 29 Aug 2008 14:09:18 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080829210815.GB21874@isi.edu> References: <20080829210815.GB21874@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10291 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 29 Aug 2008 14:09:18 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10291] AutoReply: Informtional Independent Submission: draft-leung-mip4-proxy-mode-09.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 79 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informtional Independent Submission: draft-leung-mip4-proxy-mode-09.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10291]. Please include the string: [rt.amsl.com #10291] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-leung-mip4-proxy-mode-09.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 26 September 2008. WiMAX Forum/3GPP2 Proxy Mobile IPv4 Mobile IPv4 is a standard mobility protocol that enables IPv4 device to move among networks while maintaining its IP address. The mobile device has the Mobile IPv4 client function to signal its location to the routing anchor, known as the Home Agent. However, there are many IPv4 devices without such capability due to various reasons. This document describes Proxy Mobile IPv4 (PMIPv4), a scheme based on having the Mobile IPv4 client function in a network entity to provide mobility support for an unaltered and mobility-unaware IPv4 device. This document also describes a particular application of PMIPv4 as specified in the WiMAX Forum and another application that is to be adopted in 3GPP2. This independent submision was reviewed by George Tsirtsis. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Fri Aug 29 15:05:27 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m7TM4ST2015424 for ; Fri, 29 Aug 2008 15:04:29 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0C7FF28C158; Fri, 29 Aug 2008 15:04:23 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10291 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 29 Aug 2008 15:04:24 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10291] Resolved: Informtional Independent Submission: draft-leung-mip4-proxy-mode-09.txt Status: O X-Status: X-Keywords: $Junk X-UID: 80 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Sep 9 11:06:32 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m89I5j13008374 for ; Tue, 9 Sep 2008 11:05:46 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 4F0D23A6A18; Tue, 9 Sep 2008 11:05:40 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20080909180435.GB24294@isi.edu> References: <20080909180435.GB24294@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10539 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 09 Sep 2008 11:05:40 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10539] AutoReply: Informational Independent Submission: draft-touch-msword-template-v2.0-07.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 81 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-touch-msword-template-v2.0-07.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10539]. Please include the string: [rt.amsl.com #10539] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-touch-msword-template-v2.0-07.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 7 October 2008. Version 2.0 Microsoft Word Template for Creating Internet Drafts and RFCs This document describes the properties and use of a revised Microsoft Word template (.dot) for writing Internet Drafts and RFCs. It updates the initial template described in RFC 3285 to more fully support Word's outline modes and to be easier to use. This template can be direct-printed and direct-viewed, where either is line-for-line identical with RFC Editor-compliant ASCII output. This version is intended as an update to RFC3285. The most recent version of this template and post-processing scripts are available at http://www.isi.edu/touch/tools This document was reviewed for the RFC Editor ("Independent Submissions Editor") by Mike Garhns. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Wed Oct 1 15:27:36 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m91MQpIS001966 for ; Wed, 1 Oct 2008 15:26:52 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 5C4633A68A1; Wed, 1 Oct 2008 15:26:25 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081001222534.GH11365@isi.edu> References: <20081001222534.GH11365@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10876 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 01 Oct 2008 15:26:26 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10876] AutoReply: Informational Independent Submission: draft-bberry-rfc4938bis-00.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 82 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-bberry-rfc4938bis-00.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #10876]. Please include the string: [rt.amsl.com #10876] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-bberry-rfc4938bis-00.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 29 October 2008. PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics This document extends the Point-to-Point over Ethernet (PPPoE) Protocol with an optional credit-based flow control mechanism and an optional Link Quality Metric report. These optional extensions improve the performance of PPPoE over media with variable bandwidth and limited buffering, such as mobile point-to-point radio links. This document is a minor extension to RFC 4938, to provide scaling of several fields. The RFC Editor expects that the IESG will want to attach the same IESG disclaimer to this document that they attached to 4938. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Thu Oct 2 14:38:35 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m92LbNUN019076 for ; Thu, 2 Oct 2008 14:37:24 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id A8E373A6A81; Thu, 2 Oct 2008 14:36:55 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #10876 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 02 Oct 2008 14:36:55 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #10876] Resolved: Informational Independent Submission: draft-bberry-rfc4938bis-00.txt Status: O X-Status: X-Keywords: $Junk X-UID: 83 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Oct 21 13:41:07 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9LKeii2021982 for ; Tue, 21 Oct 2008 13:40:45 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 2FB8828C194; Tue, 21 Oct 2008 13:39:28 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081021203952.GA9003@isi.edu> References: <20081021203952.GA9003@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11184 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 21 Oct 2008 13:39:29 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11184] AutoReply: Expired Internet Drafts vs. I-D Exists Status: O X-Status: X-Keywords: $NotJunk X-UID: 84 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Expired Internet Drafts vs. I-D Exists", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11184]. Please include the string: [rt.amsl.com #11184] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Hi All, There has been some discussion on how to cite expired internet-drafts on the rfc-interest list recently (please see http://mailman.rfc-editor.org/pipermail/rfc-interest/2008-October/thread.html for details -- subject: citing historic internet drafts). While doing some research, one of our editors came across what looks like an inconsistency between the Internet-Drafts Database and the I-D Tracker. Using the Internet-Drafts Database shows the I-D Status is Expired, and the I-D Tracker State is I-D Exists; however, the I-D Tracker can't find the document at all. Is this a bug? For example (using a random expired I-D name -- draft-allen-newsml-urn-rfc3085bis): https://datatracker.ietf.org/drafts/ shows the related doc info, but does not allow you to find the actual document: # View Related Documents (e.g., documents that replaced or were replaced by the subject I-D, and their derivatives and precursors.) # I-D Title: URN Namespace for NewsML Resources # I-D Status: Expired # I-D Intended Status at Publication: None # RFC Number: # I-D Tracker State: I-D Exists # Abstract: This document describes a URN (Uniform Resource Name) namespace for identifying NewsML NewsItems and NewsML related XML Schemas. A NewsItem is an information resource that is expressible as a NewsML element within a NewsML document conforming to the NewsML Document Type Declaration (DTD) as defined by the International Press Tele- communications Council (IPTC). # Author(s): The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid. If you are an author of this Internet-Draft, and if your e-mail address is not correct, then please send your current e-mail address to ietf-action@ietf.org. Danny Allen https://datatracker.ietf.org/idtracker/ shows the following error message: No matches to your query. FYI: this doesn't have any bearing (afaict) on the outcome of the discussion. We just thought we would point it out in case your to-do list ever runs low! ;) Thanks! Sandy From wwwrun@core3.amsl.com Fri Oct 24 14:52:05 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_20, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9OLpVll018307 for ; Fri, 24 Oct 2008 14:51:32 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C0E3328C186; Fri, 24 Oct 2008 14:50:08 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081024215040.GD26288@isi.edu> References: <20081024215040.GD26288@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11234 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 24 Oct 2008 14:50:08 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11234] AutoReply: RFC Online -- rfc616.txt Status: O X-Status: X-Keywords: $NotJunk X-UID: 85 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "RFC Online -- rfc616.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11234]. Please include the string: [rt.amsl.com #11234] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, Please note that a text file for RFC 616 has been added to our repository. rfc616.txt Please let us know if you have any questions. Thank you. RFC Editor From wwwrun@core3.amsl.com Fri Oct 24 15:01:15 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_05, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9OM0gLt021261 for ; Fri, 24 Oct 2008 15:00:43 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id ABF8F3A69C4; Fri, 24 Oct 2008 14:59:19 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081024220026.GE26288@isi.edu> References: <20081024220026.GE26288@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11235 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 24 Oct 2008 14:59:19 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11235] AutoReply: RFC Online -- text files Status: O X-Status: X-Keywords: $NotJunk X-UID: 86 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "RFC Online -- text files", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11235]. Please include the string: [rt.amsl.com #11235] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, Please note that the following documents were added earlier this year (around June), but we had not notified you. Please update your site as necessary. rfc158.txt rfc169.txt rfc320.txt rfc452.txt rfc493.txt rfc497.txt rfc519.txt rfc556.txt rfc557.txt rfc560.txt rfc562.txt rfc571.txt rfc573.txt rfc574.txt rfc587.txt rfc667.txt Thanks! Sandy From wwwrun@core3.amsl.com Tue Oct 28 15:57:57 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9SMvEhJ029668 for ; Tue, 28 Oct 2008 15:57:15 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 1E43D3A6970; Tue, 28 Oct 2008 15:57:14 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081028225604.GD20415@isi.edu> References: <20081028174530.931B228C335@core3.amsl.com> <20081028225604.GD20415@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11307 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Oct 2008 15:57:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11307] AutoReply: Re: Protocol Action: 'CAPWAP Access Controller DHCP Option' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 87 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'CAPWAP Access Controller DHCP Option' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11307]. Please include the string: [rt.amsl.com #11307] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Oct 28, 2008 at 10:45:30AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'CAPWAP Access Controller DHCP Option ' > as a Proposed Standard > > This document is the product of the Control And Provisioning of Wireless > Access Points Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-capwap-dhc-ac-option-02.txt > > Technical Summary > > The Control And Provisioning of Wireless Access Points Protocol > allows a Wireless Termination Point to use DHCP to discover the > Access Controllers it is to connect to. This document describes the > DHCP options to be used by the CAPWAP protocol. > > Working Group Summary > > This document is a work item of the CAPWAP WG and respresents > the consensus of the group. > > Document Quality > > This document was reviewed within the CAPWAP WG and no issues > were raised in WG Last Call. Francis Dupont reviewed it for the GenART > and Dan Romascanu performed the OPS Area Director review. > > Personnel > > Margaret Wasserman is the document shepherd and Dan Romascanu is the > responsible AD. From wwwrun@core3.amsl.com Tue Oct 28 15:58:04 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_00, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES,SUBJ_HAS_UNIQ_ID autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9SMvLWw029694 for ; Tue, 28 Oct 2008 15:57:22 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 9387A3A6968; Tue, 28 Oct 2008 15:57:21 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081028225624.GE20415@isi.edu> References: <20081027220207.DEEF83A6A2C@core3.amsl.com> <20081028225624.GE20415@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11308 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Oct 2008 15:57:21 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11308] AutoReply: Re: Document Action: 'Requirements for Management of Overload in the Session Initiation Protocol' to Informational RFC Status: O X-Status: X-Keywords: $NotJunk X-UID: 88 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Document Action: 'Requirements for Management of Overload in the Session Initiation Protocol' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11308]. Please include the string: [rt.amsl.com #11308] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Oct 27, 2008 at 03:02:07PM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Requirements for Management of Overload in the Session Initiation > Protocol ' > as an Informational RFC > > This document is the product of the Session Initiation Proposal > Investigation Working Group. > > The IESG contact persons are Jon Peterson and Cullen Jennings. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-sipping-overload-reqs-05.txt > > Technical Summary > > Overload occurs in Session Initiation Protocol (SIP) networks when > proxies and user agents have insuffient resources to complete the > processing of a request. SIP provides limited support for overload > handling through its 503 response code, which tells an upstream > element that it is overloaded. However, numerous problems have been > identified with this mechanism. This draft summarizes the problems > with the existing 503 mechanism, and provides some requirements for a > solution. > > Working Group Summary > > The SIPPING WG supports the development and advancement of > this document. > > Document Quality > > This document defines no new protocol elements. The document has been > thoroughly reviewed by members of the SIPPING WG and members of the design > team working on modeling and simulations for SIP overload. > > > Personnel > > Jon Peterson reviewed this document for the IESG. Mary Barnes in the > document shepherd. > > RFC Editor Note > > In the Security Considerations, please append the following paragraph: > > Any mechanism that improves the behavior of SIP elements under load > will result in more predictable performance in the face of > application-layer denial-of-service attacks. From wwwrun@core3.amsl.com Tue Oct 28 16:04:27 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: * X-Spam-Status: No, score=1.2 required=5.0 tests=AWL,BAYES_50, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9SN3naC002528 for ; Tue, 28 Oct 2008 16:03:50 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0FAB73A6C96; Tue, 28 Oct 2008 16:03:49 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11307 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Oct 2008 16:03:50 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11307] Resolved: Re: Protocol Action: 'CAPWAP Access Controller DHCP Option' to Proposed Standard Status: O X-Status: X-Keywords: $Junk X-UID: 89 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Oct 28 16:07:43 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_20, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES,SUBJ_HAS_UNIQ_ID autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9SN7C6B003935 for ; Tue, 28 Oct 2008 16:07:13 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 736B03A6C7F; Tue, 28 Oct 2008 16:07:12 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11308 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Oct 2008 16:07:12 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11308] Resolved: Re: Document Action: 'Requirements for Management of Overload in the Session Initiation Protocol' to Informational RFC Status: O X-Status: X-Keywords: $Junk X-UID: 90 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Oct 28 16:09:15 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9SN8XI2004277 for ; Tue, 28 Oct 2008 16:08:34 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 4AE3A3A6C93; Tue, 28 Oct 2008 16:08:33 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081028225639.GF20415@isi.edu> References: <20081027190847.3436C3A67D4@core3.amsl.com> <20081028225639.GF20415@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11309 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Oct 2008 16:08:34 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11309] AutoReply: Re: Protocol Action: 'Textual Representation of AS Numbers' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 91 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Textual Representation of AS Numbers' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11309]. Please include the string: [rt.amsl.com #11309] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Oct 27, 2008 at 12:08:47PM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Textual Representation of AS Numbers ' > as a Proposed Standard > > This document is the product of the Inter-Domain Routing Working Group. > > The IESG contact persons are David Ward and Ross Callon. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-idr-as-representation-01.txt > > Technical Summary > > A textual representation for Autonomous System (AS) numbers is > defined as the decimal value of the AS Number. This textual > representation is to be used by all documents, systems and user > interfaces referring to AS numbers. > > > asplain > refers to a syntax scheme of representing all AS numbers using > decimal integer notation. Using asplain notation an AS number of > value 65526 would be represented as the string "65526" and an AS > number of value 65546 would be represented as the string "65546". > > Working Group Summary > > It was readily accepted. > > Document Quality > > No issues > > Personnel > > Dave Ward From wwwrun@core3.amsl.com Tue Oct 28 16:16:52 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_40, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9SNGIvI006908 for ; Tue, 28 Oct 2008 16:16:19 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 308F03A6970; Tue, 28 Oct 2008 16:16:15 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11309 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Oct 2008 16:16:16 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11309] Resolved: Re: Protocol Action: 'Textual Representation of AS Numbers' to Proposed Standard Status: O X-Status: X-Keywords: $Junk X-UID: 92 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Oct 29 11:35:14 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9TIYGxI008004 for ; Wed, 29 Oct 2008 11:34:17 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 7584E28C3BD; Wed, 29 Oct 2008 11:34:16 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@iesg.org In-Reply-To: <20081029183208.GD15253@isi.edu> References: <20081029161324.E6B423A6D3E@core3.amsl.com> <20081029183208.GD15253@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11331 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Oct 2008 11:34:16 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11331] AutoReply: Re: Protocol Action: 'Information Model and XML Data Model for Traceroute Measurements' to Proposed Standard Status: O X-Status: X-Keywords: $NotJunk X-UID: 93 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Information Model and XML Data Model for Traceroute Measurements' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11331]. Please include the string: [rt.amsl.com #11331] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@iesg.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Oct 29, 2008 at 09:13:24AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Information Model and XML Data Model for Traceroute Measurements ' > as a Proposed Standard > > This document is the product of the IP Performance Metrics Working Group. > > The IESG contact persons are Lars Eggert and Magnus Westerlund. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ippm-storetraceroutes-12.txt > > Technical Summary > > This document describes a standard way to store the configuration and > the results of traceroute measurements. This document first of all > describes the tool itself; afterwards, the common information model > is defined dividing the information elements in two semantically > separated groups (configuration elements and results ones). Moreover > an additional element is defined to relate configuration elements and > results ones by means of a common unique identifier. On the basis of > the information model a data model based on XML is defined to store > the results of traceroute measurements. > > Working Group Summary > > The working group has supported the document throughout its life > and it has been uncontroversial. > > Document Quality > > The document has been given thorough review by the group over its > revisions. The XML code has been reviewed by the XML directorate. > > A previous version of this document required significant changes to > address the gen-art review. The document underwent a second > working group last call and IETF last call to verify consensus for > these changes. > > Personnel > > Henk Uijterwaal (henk@ripe.net) was the Document Shepherd. > Ned Freed (ned.freed@mrochek.com) reviewed the document > for the XML Directorate. Lars Eggert (lars.eggert@nokia.com) > reviewed it for the IESG. > > RFC Editor Note > > In the description of the CtlSourceAddress element (bottom of page 29): > > > OLD: > On hosts with more than one IP address, this option can be used to > force the source address to be something other than the primary IP > address of the interface the probe is sent on. If "unknown" is > specified for this object it means that source address specification > was disabled. > > NEW: > On hosts with more than one IP address, this option can be used in > "RequestMetadata" element to force the source address to be something > other than the primary IP address of the interface the probe is sent > on; the value "unknown" means the default address will be used. From wwwrun@core3.amsl.com Wed Oct 29 13:54:45 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_05, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m9TKsCf7019259 for ; Wed, 29 Oct 2008 13:54:13 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 8927A3A6B2D; Wed, 29 Oct 2008 13:54:12 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@iesg.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11331 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Oct 2008 13:54:12 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11331] Resolved: Re: Protocol Action: 'Information Model and XML Data Model for Traceroute Measurements' to Proposed Standard Status: O X-Status: X-Keywords: $Junk X-UID: 94 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Mon Nov 3 12:30:09 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_40, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mA3KTdiw028788 for ; Mon, 3 Nov 2008 12:29:40 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id DFC073A6B8F; Mon, 3 Nov 2008 12:29:40 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20081103202850.GB28198@isi.edu> References: <20081103202850.GB28198@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11457 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 03 Nov 2008 12:29:40 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11457] AutoReply: Please expire these drafts Status: O X-Status: X-Keywords: $NotJunk X-UID: 95 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Please expire these drafts", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11457]. Please include the string: [rt.amsl.com #11457] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, Please allow the following documents to expire in the I-D repository: draft-bberry-pppoe-scaled-credits-metrics-01.txt draft-bambenek-doubleflux-01.txt Please let us know if you have any questions. Thank you. RFC Editor From wwwrun@core3.amsl.com Mon Nov 3 12:39:08 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_40, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mA3KccS5002600 for ; Mon, 3 Nov 2008 12:38:39 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 498CA28C2E6; Mon, 3 Nov 2008 12:38:29 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20081103203623.GD28198@isi.edu> References: <20081103203623.GD28198@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11458 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 03 Nov 2008 12:38:30 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11458] AutoReply: Please expire this draft Status: O X-Status: X-Keywords: $NotJunk X-UID: 96 Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Please expire this draft", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11458]. Please include the string: [rt.amsl.com #11458] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, Please allow draft-shore-nls-tl-06.txt to expire. Thank you. RFC Editor From wwwrun@core3.amsl.com Mon Nov 3 15:51:57 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: * X-Spam-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_50, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mA3NpXag018322 for ; Mon, 3 Nov 2008 15:51:34 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 6FAE83A6CB1; Mon, 3 Nov 2008 15:51:32 -0800 (PST) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11458 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 03 Nov 2008 15:51:32 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11458] Resolved: Please expire this draft Status: O X-Status: X-Keywords: $Junk X-UID: 97 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Mon Nov 3 15:53:55 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_50, DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mA3Nr5Rb019010 for ; Mon, 3 Nov 2008 15:53:06 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 134B63A6CB2; Mon, 3 Nov 2008 15:53:07 -0800 (PST) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11457 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 03 Nov 2008 15:53:07 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11457] Resolved: Please expire these drafts Status: O X-Status: X-Keywords: $Junk X-UID: 98 According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Nov 11 18:05:53 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mAC24bvd017526 for ; Tue, 11 Nov 2008 18:04:38 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id DBE2E3A6A7F; Tue, 11 Nov 2008 18:04:35 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20081112020415.GC16949@isi.edu> References: <20081111172037.34D0328C1F2@core3.amsl.com> <20081112020415.GC16949@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11638 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 11 Nov 2008 18:04:35 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11638] AutoReply: Re: Protocol Action: 'CAPWAP Protocol Specification' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'CAPWAP Protocol Specification' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #11638]. Please include the string: [rt.amsl.com #11638] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Nov 11, 2008 at 09:20:37AM -0800, The IESG wrote: > The IESG has approved the following document: > > - 'CAPWAP Protocol Specification ' > as a Proposed Standard > > This document is the product of the Control And Provisioning of Wireless > Access Points Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-capwap-protocol-specification-15.txt > > Technical Summary > > This specification defines the Control And Provisioning of Wireless > Access Points (CAPWAP) Protocol. This is a protocol to allow an > Access Controller (AC) to securely manage the firmware and > configuration of a set of Wireless Termination Points (WTPs). > > The CAPWAP protocol meets the IETF CAPWAP working group protocol > requirements. The CAPWAP protocol is designed to be flexible, > allowing it to be used for a variety of wireless technologies. > This document describes the base CAPWAP protocol. The CAPWAP > protocol binding which defines extensions for use with the IEEE > 802.11 wireless LAN protocol is available in a separate document. > Extensions are expected to be defined to enable use of the CAPWAP > protocol with additional wireless technologies. > > Working Group Summary > > This document represents a very strong consensus of the WG. Earlier > there was a lot of contention about different aspects of this > protocol, including (but not limited to) the security model, the basic > operational model, and what parts of the functionality should be > mandatory or optional. However, consensus was reached > on all of those points and that consensus is properly reflected in the > current document. > > Document Quality > > The CAPWAP protocol has been extensively reviewed and has been > updated to address issues raised in those reviewes. Technical > advisors were Charles Clancy, Scott Kelly, Bob O'Hara and David > Borman. Joe Salowey provided an early secdir review, and > Pasi Eronen reviewed again at IETF Last Call. Magnus Westerlund and > Lars Eggert performed an early transport area review. Dan Romascanu > performed the OPS Area Review. The document was also reviewed by > IEEE 802.11. > > Personnel > > Margaret Wasserman is PROTO-shepherd and Dan Romascanu is shepherding > AD. From wwwrun@core3.amsl.com Wed Nov 12 10:40:18 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: * X-Spam-Status: No, score=1.4 required=5.0 tests=AWL,BAYES_50, DNS_FROM_SECURITYSAGE,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mACIddpd020738 for ; Wed, 12 Nov 2008 10:39:40 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 5CBF63A6931; Wed, 12 Nov 2008 10:39:38 -0800 (PST) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #11638 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 12 Nov 2008 10:39:38 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #11638] Resolved: Re: Protocol Action: 'CAPWAP Protocol Specification' to Proposed Standard According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From root@core3.amsl.com Fri Dec 5 08:00:46 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES, SUBJ_HAS_UNIQ_ID autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mB5FxvNG001787 for ; Fri, 5 Dec 2008 07:59:58 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 0) id C89643A67AE; Fri, 5 Dec 2008 08:00:01 -0800 (PST) From: IESG Secretary To: rfc-editor@rfc-editor.org Cc: avezza@amsl.com, cmorgan@amsl.com, iesg@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20081205160001.C89643A67AE@core3.amsl.com> Date: Fri, 5 Dec 2008 08:00:01 -0800 (PST) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: root@core3.amsl.com Subject: Expedited Handling Request for the CAPWAP Protocol Specification (draft-ietf-capwap-protocol-specification) RFC Editor, The IESG approved in a management item discussion in the 12/4 telechat the request to expedite processing of the CAPWAP Protocol Specification (draft-ietf-capwap-protocol-specification) which was recently approved by the IESG. Please do the best that this specification is published until 12/23, or soon after 1/2/2009. Background: An industry standards group, EPCglobal, has a CAPWAP binding, "EPCglobal Discovery, Configuration and Initialization (DCI)" that cannot be published until they have an RFC number for the CAPWAP Protocol Specification. The DCI specification is fully ratified and their final publication has been blocking on the publication of the CAPWAP Protocol Specification since mid-summer. Thanks and Regards, Dan From root@core3.amsl.com Mon Dec 15 11:00:57 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mBFIxttx011480 for ; Mon, 15 Dec 2008 10:59:56 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 0) id 0D02D28C131; Mon, 15 Dec 2008 11:00:01 -0800 (PST) From: IESG Secretary To: rfc-editor@rfc-editor.org Cc: iesg@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20081215190002.0D02D28C131@core3.amsl.com> Date: Mon, 15 Dec 2008 11:00:02 -0800 (PST) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: root@core3.amsl.com Subject: Expedited Handling of draft-ietf-avt-rtp-g719 To the RFC Editor: The IESG has approved expedited publication for draft-ietf-avt-rtp-g719 and the preferred publication date is by January 15, 2009. Thank you. Best regards, IESG Secretary From root@core3.amsl.com Tue Dec 23 13:15:23 2008 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES, SUBJ_HAS_UNIQ_ID autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id mBNLEr1X010917 for ; Tue, 23 Dec 2008 13:14:54 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 0) id 989943A6859; Tue, 23 Dec 2008 13:15:01 -0800 (PST) From: IESG Secretary To: rfc-editor@rfc-editor.org Cc: iesg@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20081223211501.989943A6859@core3.amsl.com> Date: Tue, 23 Dec 2008 13:15:01 -0800 (PST) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: root@core3.amsl.com Subject: Expedited publishing request for draft-jerichow-msec-mikey-genext-oma To the RFC Editor, The IESG has approved the request for expedited publishing for draft-jerichow-msec-mikey-genext-oma, with a target date of January 7, 2009, to establish a stable reference for the Open Mobile Alliance to use in their own publications. Thank you, The IESG Secretary From wwwrun@core3.amsl.com Wed Feb 25 13:15:33 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n1PLEitj020353 for ; Wed, 25 Feb 2009 13:14:45 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id AA7F03A6A9E; Wed, 25 Feb 2009 13:14:23 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090225211308.GO13275@isi.edu> References: <20090225211308.GO13275@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13469 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 25 Feb 2009 13:14:23 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13469] AutoReply: Informational Independent Submission: ID-stringIndependent Submission: draft-farah-adntf-ling-guidelines-04.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: ID-stringIndependent Submission: draft-farah-adntf-ling-guidelines-04.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #13469]. Please include the string: [rt.amsl.com #13469] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-farah-adntf-ling-guidelines-04.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Five week timeout expires on 1 April 2009. Note that we have included an extra week because of the upcoming IETF. Linguistic Guidelines for the Use of the Arabic Language in Internet Domains This document constitutes technical specifications for the use of Arabic in Internet Domain names and provides linguistic guidelines for Arabic Domain Names. It addresses Arabic-specific linguistic issues pertaining to the use of Arabic language in domain names. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Thu Feb 26 12:53:41 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n1QKqwPJ002287 for ; Thu, 26 Feb 2009 12:52:59 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 4D26D28C2DB; Thu, 26 Feb 2009 12:52:35 -0800 (PST) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13469 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 26 Feb 2009 12:52:36 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13469] Resolved: Informational Independent Submission: ID-stringIndependent Submission: draft-farah-adntf-ling-guidelines-04.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu Mar 5 09:44:45 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n25Hi98K009747 for ; Thu, 5 Mar 2009 09:44:10 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id AD78928C3B9; Thu, 5 Mar 2009 09:43:39 -0800 (PST) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090305174320.GB10127@isi.edu> References: <20090305174320.GB10127@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13665 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 05 Mar 2009 09:43:39 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13665] AutoReply: Re: PWE mib -- draft-vainshtein-pwe3-tdm-control-protocol-extensi Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: PWE mib -- draft-vainshtein-pwe3-tdm-control-protocol-extensi", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #13665]. Please include the string: [rt.amsl.com #13665] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Hi All! I wasn't sure if this should be sent to you or to webtools@ietf.org, but I thought I'd try you first. I'm also not sure there is any action required, but there seems to be an oddity in the search results for draft-vainshtein-pwe3-tdm-control-protocol-extensi using the Internet-Drafts Database. We were notified that draft-vainshtein-pwe3-tdm-control-protocol-extensi was replaced by draft-ietf-pwe3-tdm-control-protocol-extensi-07, but the results from the Internet-Drafts Database Interface do not show that the draft was replaced. It yields the following: I-D Filename and Version Number draft-vainshtein-pwe3-tdm-control-protocol-extensi-04 Submission Date 2005-07-06 Status Expired RFC # I-D Tracker State I-D Exists It seems that when a draft has been replaced, the Internet-Drafts database usually indicates that the I-D has been replaced? The results were a bit confusing because it lists the Status as Expired, but the I-D Tracker State as I-D Exists, even though the I-D Tracker results in "No matches to your query." Thanks! See you in a couple of weeks! Sandy > On Mar 5, 2009, at 8:22 AM, Orly Nicklass wrote: > > >HI, > > > >I review the publication list and noticed that some of the > >information is not accurate. The not received draft is in the > >repository, I put reference to it. And one is already RFC by now. > > > >Pls advice how to adjust those states correctly > > > > > >2008-07-21 draft-ietf-pwe3-enet-mib-13.txt PLS see new > >draft: http://www.ietf.org/internet-drafts/draft-ietf-pwe3-enet- > >mib-14.txt MISSREFREF draft-ietf-pwe3-pw-mib IN-QUEUE > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-15.txtD. > >Zelig, Ed., T. Nadeau, Ed."Ethernet Pseudowire (PW) Management > >Information Base (MIB)"Bytes: 44473Working Group: Pseudo Wire > >Emulation Edge to Edge > > > > > >2008-06-23 draft-ietf-pwe3-pw-mib-14.txtMISSREFREF draft- > >ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-15.txtT. > >Nadeau, Ed., D. Zelig, Ed."Pseudowire (PW) Management Information > >Base (MIB)"Bytes: 128939Working Group: Pseudo Wire Emulation Edge > >to Edge > > > > > >2008-11-18 draft-ietf-pwe3-pw-atm-mib-06.txtMISSREFREF > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc- > >mib-15.txt draft-ietf-pwe3-pw-mib IN-QUEUE draft-ietf- > >pwe3-pw-mpls-mib IN-QUEUEO. Nicklass, S. Sathappan, M. > >Venkatesan, T. Nadeau"Managed Objects for ATM over Packet Switched > >Network (PSN)"Bytes: 73158Working Group: Pseudo Wire Emulation Edge > >to Edge > > > >2009-02-09 draft-ietf-pwe3-tdm-mib-11.txtMISSREFREF draft- > >vainshtein-pwe3-tdm-control-protocol-extensi NOT-RECEIVED this > >RFC by now: http://www.ietf.org/rfc/rfc5287.txt draft-ietf- > >pwe3-pw-mib IN-QUEUE draft-ietf-pwe3-pw-tc-mib NOT- > >RECEIVED pls see: http://www.ietf.org/internet-drafts/draft-ietf- > >pwe3-pw-tc-mib-15.txtO. Nicklass"Managed Objects for TDM over > >Packet Switched Network (PSN)"Bytes: 81329Working Group: Pseudo > >Wire Emulation Edge to Edge > > > > > >2008-07-21 draft-ietf-pwe3-pw-mpls-mib-14.txtMISSREFREF > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc- > >mib-15.txt draft-ietf-pwe3-pw-mib IN-QUEUED. Zelig, Ed., T. > >Nadeau, Ed."Pseudowire (PW) over MPLS PSN Management Information > >Base (MIB)"Bytes: 62692Working Group: Pseudo Wire Emulation Edge to > >Edge > > > > > > > > > >Orly Nicklass, Ph.D > >VP R&D, NBU > >RADVISION® > >Delivering the Visual ExperienceTM > >Phone: +97237679444 > >Mobile: 0547769444 > > > ----- End forwarded message ----- From wwwrun@core3.amsl.com Thu Mar 5 11:33:36 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n25JWvI4020139 for ; Thu, 5 Mar 2009 11:32:58 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 7376728C0DD; Thu, 5 Mar 2009 11:32:27 -0800 (PST) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090305174320.GB10127@isi.edu> References: <20090305174320.GB10127@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13665 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 05 Mar 2009 11:32:27 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13665] Re: PWE mib -- draft-vainshtein-pwe3-tdm-control-protocol-extensi Hi Sandy, It looks like what happened in this case is that somehow the secretariat missed the message that draft-vainshtein-pwe3-tdm-control-protocol-extensi was replaced by draft-ietf-pwe3-tdm-control-protocol-extensi. That's now been fixed, and so the search results for draft-vainshtein show the draft as being Replaced/ID Exists. Best regards, Cindy On Thu Mar 05 09:43:39 2009, rfc-editor@rfc-editor.org wrote: > Hi All! > > I wasn't sure if this should be sent to you or to webtools@ietf.org, > but I thought I'd try you first. I'm also not sure there is any > action required, but there seems to be an oddity in the search results > for draft-vainshtein-pwe3-tdm-control-protocol-extensi using the > Internet-Drafts Database. > > We were notified that > draft-vainshtein-pwe3-tdm-control-protocol-extensi was replaced by > draft-ietf-pwe3-tdm-control-protocol-extensi-07, but the results from > the Internet-Drafts Database Interface do not show that the draft was > replaced. It yields the following: > > I-D Filename and Version Number > draft-vainshtein-pwe3-tdm-control-protocol-extensi-04 > > Submission Date > 2005-07-06 > > Status > Expired > > RFC # > > I-D Tracker State > I-D Exists > > It seems that when a draft has been replaced, the Internet-Drafts > database usually indicates that the I-D has been replaced? > > The results were a bit confusing because it lists the Status as > Expired, but the I-D Tracker State as I-D Exists, even though the I-D > Tracker results in "No matches to your query." > > Thanks! See you in a couple of weeks! > > Sandy > > > On Mar 5, 2009, at 8:22 AM, Orly Nicklass wrote: > > > > >HI, > > > > > >I review the publication list and noticed that some of the > > >information is not accurate. The not received draft is in the > > >repository, I put reference to it. And one is already RFC by now. > > > > > >Pls advice how to adjust those states correctly > > > > > > > > >2008-07-21 draft-ietf-pwe3-enet-mib-13.txt PLS see new > > >draft: http://www.ietf.org/internet-drafts/draft-ietf-pwe3-enet- > > >mib-14.txt MISSREFREF draft-ietf-pwe3-pw-mib IN-QUEUE > > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-15.txtD. > > >Zelig, Ed., T. Nadeau, Ed."Ethernet Pseudowire (PW) Management > > >Information Base (MIB)"Bytes: 44473Working Group: Pseudo Wire > > >Emulation Edge to Edge > > > > > > > > >2008-06-23 draft-ietf-pwe3-pw-mib-14.txtMISSREFREF draft- > > >ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-15.txtT. > > >Nadeau, Ed., D. Zelig, Ed."Pseudowire (PW) Management Information > > >Base (MIB)"Bytes: 128939Working Group: Pseudo Wire Emulation Edge > > >to Edge > > > > > > > > >2008-11-18 draft-ietf-pwe3-pw-atm-mib-06.txtMISSREFREF > > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc- > > >mib-15.txt draft-ietf-pwe3-pw-mib IN-QUEUE draft-ietf- > > >pwe3-pw-mpls-mib IN-QUEUEO. Nicklass, S. Sathappan, M. > > >Venkatesan, T. Nadeau"Managed Objects for ATM over Packet Switched > > >Network (PSN)"Bytes: 73158Working Group: Pseudo Wire Emulation Edge > > >to Edge > > > > > >2009-02-09 draft-ietf-pwe3-tdm-mib-11.txtMISSREFREF draft- > > >vainshtein-pwe3-tdm-control-protocol-extensi NOT-RECEIVED this > > >RFC by now: http://www.ietf.org/rfc/rfc5287.txt draft-ietf- > > >pwe3-pw-mib IN-QUEUE draft-ietf-pwe3-pw-tc-mib NOT- > > >RECEIVED pls see: http://www.ietf.org/internet-drafts/draft-ietf- > > >pwe3-pw-tc-mib-15.txtO. Nicklass"Managed Objects for TDM over > > >Packet Switched Network (PSN)"Bytes: 81329Working Group: Pseudo > > >Wire Emulation Edge to Edge > > > > > > > > >2008-07-21 draft-ietf-pwe3-pw-mpls-mib-14.txtMISSREFREF > > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc- > > >mib-15.txt draft-ietf-pwe3-pw-mib IN-QUEUED. Zelig, Ed., T. > > >Nadeau, Ed."Pseudowire (PW) over MPLS PSN Management Information > > >Base (MIB)"Bytes: 62692Working Group: Pseudo Wire Emulation Edge to > > >Edge > > > > > > > > > > > > > > >Orly Nicklass, Ph.D > > >VP R&D, NBU > > >RADVISION® > > >Delivering the Visual ExperienceTM > > >Phone: +97237679444 > > >Mobile: 0547769444 > > > > > > > ----- End forwarded message ----- > From wwwrun@core3.amsl.com Thu Mar 5 11:59:31 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n25JwjTY029701 for ; Thu, 5 Mar 2009 11:58:46 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id D460C3A6B3F; Thu, 5 Mar 2009 11:58:15 -0800 (PST) Subject: Re: [rt.amsl.com #13665] Re: PWE mib -- draft-vainshtein-pwe3-tdm-control-protocol-extensi From: "RFC Editor via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090305195744.GD10127@isi.edu> References: <20090305174320.GB10127@isi.edu> <20090305195744.GD10127@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13665 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 05 Mar 2009 11:58:15 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Hi Cindy, Thanks for the info and for the quick response! Sandy On Thu, Mar 05, 2009 at 11:32:27AM -0800, Cindy Morgan via RT wrote: > Hi Sandy, > > It looks like what happened in this case is that somehow the secretariat > missed the message that > draft-vainshtein-pwe3-tdm-control-protocol-extensi was replaced by > draft-ietf-pwe3-tdm-control-protocol-extensi. That's now been fixed, > and so the search results for draft-vainshtein show the draft as being > Replaced/ID Exists. > > Best regards, > Cindy > > > On Thu Mar 05 09:43:39 2009, rfc-editor@rfc-editor.org wrote: > > Hi All! > > > > I wasn't sure if this should be sent to you or to webtools@ietf.org, > > but I thought I'd try you first. I'm also not sure there is any > > action required, but there seems to be an oddity in the search results > > for draft-vainshtein-pwe3-tdm-control-protocol-extensi using the > > Internet-Drafts Database. > > > > We were notified that > > draft-vainshtein-pwe3-tdm-control-protocol-extensi was replaced by > > draft-ietf-pwe3-tdm-control-protocol-extensi-07, but the results from > > the Internet-Drafts Database Interface do not show that the draft was > > replaced. It yields the following: > > > > I-D Filename and Version Number > > draft-vainshtein-pwe3-tdm-control-protocol-extensi-04 > > > > Submission Date > > 2005-07-06 > > > > Status > > Expired > > > > RFC # > > > > I-D Tracker State > > I-D Exists > > > > It seems that when a draft has been replaced, the Internet-Drafts > > database usually indicates that the I-D has been replaced? > > > > The results were a bit confusing because it lists the Status as > > Expired, but the I-D Tracker State as I-D Exists, even though the I-D > > Tracker results in "No matches to your query." > > > > Thanks! See you in a couple of weeks! > > > > Sandy > > > > > On Mar 5, 2009, at 8:22 AM, Orly Nicklass wrote: > > > > > > >HI, > > > > > > > >I review the publication list and noticed that some of the > > > >information is not accurate. The not received draft is in the > > > >repository, I put reference to it. And one is already RFC by now. > > > > > > > >Pls advice how to adjust those states correctly > > > > > > > > > > > >2008-07-21 draft-ietf-pwe3-enet-mib-13.txt PLS see new > > > >draft: http://www.ietf.org/internet-drafts/draft-ietf-pwe3-enet- > > > >mib-14.txt MISSREFREF draft-ietf-pwe3-pw-mib IN-QUEUE > > > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-15.txtD. > > > >Zelig, Ed., T. Nadeau, Ed."Ethernet Pseudowire (PW) Management > > > >Information Base (MIB)"Bytes: 44473Working Group: Pseudo Wire > > > >Emulation Edge to Edge > > > > > > > > > > > >2008-06-23 draft-ietf-pwe3-pw-mib-14.txtMISSREFREF draft- > > > >ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-15.txtT. > > > >Nadeau, Ed., D. Zelig, Ed."Pseudowire (PW) Management Information > > > >Base (MIB)"Bytes: 128939Working Group: Pseudo Wire Emulation Edge > > > >to Edge > > > > > > > > > > > >2008-11-18 draft-ietf-pwe3-pw-atm-mib-06.txtMISSREFREF > > > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc- > > > >mib-15.txt draft-ietf-pwe3-pw-mib IN-QUEUE draft-ietf- > > > >pwe3-pw-mpls-mib IN-QUEUEO. Nicklass, S. Sathappan, M. > > > >Venkatesan, T. Nadeau"Managed Objects for ATM over Packet Switched > > > >Network (PSN)"Bytes: 73158Working Group: Pseudo Wire Emulation Edge > > > >to Edge > > > > > > > >2009-02-09 draft-ietf-pwe3-tdm-mib-11.txtMISSREFREF draft- > > > >vainshtein-pwe3-tdm-control-protocol-extensi NOT-RECEIVED this > > > >RFC by now: http://www.ietf.org/rfc/rfc5287.txt draft-ietf- > > > >pwe3-pw-mib IN-QUEUE draft-ietf-pwe3-pw-tc-mib NOT- > > > >RECEIVED pls see: http://www.ietf.org/internet-drafts/draft-ietf- > > > >pwe3-pw-tc-mib-15.txtO. Nicklass"Managed Objects for TDM over > > > >Packet Switched Network (PSN)"Bytes: 81329Working Group: Pseudo > > > >Wire Emulation Edge to Edge > > > > > > > > > > > >2008-07-21 draft-ietf-pwe3-pw-mpls-mib-14.txtMISSREFREF > > > >draft-ietf-pwe3-pw-tc-mib NOT-RECEIVED pls see: http:// > > > >www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc- > > > >mib-15.txt draft-ietf-pwe3-pw-mib IN-QUEUED. Zelig, Ed., T. > > > >Nadeau, Ed."Pseudowire (PW) over MPLS PSN Management Information > > > >Base (MIB)"Bytes: 62692Working Group: Pseudo Wire Emulation Edge to > > > >Edge > > > > > > > > > > > > > > > > > > > >Orly Nicklass, Ph.D > > > >VP R&D, NBU > > > >RADVISION? > > > >Delivering the Visual ExperienceTM > > > >Phone: +97237679444 > > > >Mobile: 0547769444 > > > > > > > > > > > ----- End forwarded message ----- > > > > From wwwrun@core3.amsl.com Thu Mar 5 12:33:17 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n25KVrEM012547 for ; Thu, 5 Mar 2009 12:31:54 -0800 (PST) Received: by core3.amsl.com (Postfix, from userid 30) id 027693A6BB8; Thu, 5 Mar 2009 12:31:22 -0800 (PST) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13665 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 05 Mar 2009 12:31:22 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13665] Resolved: Re: PWE mib -- draft-vainshtein-pwe3-tdm-control-protocol-extensi According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu Mar 12 12:51:44 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES, SUBJ_HAS_UNIQ_ID autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2CJp2sl026936 for ; Thu, 12 Mar 2009 12:51:03 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 50F783A6A73; Thu, 12 Mar 2009 12:50:24 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090312185017.GC7242@isi.edu> References: <49B94385.1060609@secunet.com> <20090312185017.GC7242@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13888 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 12 Mar 2009 12:50:24 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13888] AutoReply: Re: [Fwd: New Version Notification - draft-lochter-pkix-brainpool-ecc-03.txt] Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: [Fwd: New Version Notification - draft-lochter-pkix-brainpool-ecc-03.txt]", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #13888]. Please include the string: [rt.amsl.com #13888] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, Please note that a new version of this document has been submitted. The author notified us that version -03 is now available. Thank you. RFC Editor On Thu, Mar 12, 2009 at 06:16:53PM +0100, Johannes Merkle wrote: > Dear RFC Editors, > > version 03 includes all changes requested by the reviewers (Alfred Hoenes and Gerhard Frey) we agreed on with Bob > Braden. Thus, we think that the draft is ready to be published as an RFC. Please inform us how to proceed. > > Best regards, > Johannes Merkle > > > > > > -------- Original Message -------- > Subject: New Version Notification - draft-lochter-pkix-brainpool-ecc-03.txt > Date: Fri, 6 Mar 2009 16:30:02 -0800 (PST) > From: ID Tracker > To: manfred.lochter@bsi.bund.de, johannes.merkle@secunet.com, > draft-lochter-pkix-brainpool-ecc@tools.ietf.org,tim.polk@nist.gov > > New version (-03) has been submitted for draft-lochter-pkix-brainpool-ecc-03.txt. > http://www.ietf.org/internet-drafts/draft-lochter-pkix-brainpool-ecc-03.txt > > > > IETF Secretariat. From wwwrun@core3.amsl.com Fri Mar 13 09:10:55 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2DG9jej006562 for ; Fri, 13 Mar 2009 09:09:45 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 1388728C189; Fri, 13 Mar 2009 09:09:05 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090313160825.GD6570@isi.edu> References: <49ba7c46.47c1f10a.082b.ffffe863@mx.google.com> <20090313160825.GD6570@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13912 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 13 Mar 2009 09:09:06 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13912] AutoReply: Re: Author info change for three drafts in your queue Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Author info change for three drafts in your queue", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #13912]. Please include the string: [rt.amsl.com #13912] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Hi Tom and IESG Secretariat*, Thanks for providing us with your updated email address. a) We have updated our database and the documents to reflect your new address. However, when the documents reach AUTH48, we expect that you may want to change your street address as well. b*) We are unsure whether there is an IETF author's database. We are including the IETF Secretariat in this thread in the hopes that they can provide you with that information. c) There is no issue with our processing the documents with/without the RFC 5378 copyright at this time. You do not need to resubmit your documents since they have already been approved for publication and are in our queue. During the transition to the RFC 5378 copyright notice and legends, we are updating the text with the new RFC 5378 copyright notice, and including the optional 6.c.iii paragrph by default for I-Ds that were submitted with the pre-RFC-5378 copyright. During AUTH48, you will have the opportunity to tell us whether the optional 6.c.iii is not necessary and can be deleted. Please let us know if you have any questions. Thanks! RFC Editor/sg On Fri, Mar 13, 2009 at 11:30:47AM -0400, Tom Talpey wrote: > I am a co-author of three drafts from the NFSv4 working group > which are in the editor's queue. I am, however, no longer at > NetApp, to which the drafts and probably your database point. > > So, I'd like to: > a) let you know my current best address (above), and > b) ask whether there is some other registry I need to > change - the IETF author's database? > > The drafts in question are: > draft-ietf-nfsv4-nfs-rdma-problem-statement > draft-ietf-nfsv4-rpcrdma > draft-ietf-nfsv4-nfsdirect > > Oh, one other question perhaps. Of the three, only -rpcrdma uses > the new RFC5378 assignment text. Is there any issue with the > other two; should they be updated, or do they proceed as-is? > > The source for these three drafts is available on request. They've > been in the works for a long time, so they are in nroff format. > > Tom. From wwwrun@core3.amsl.com Wed Mar 25 10:52:20 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2PHp7dS015399 for ; Wed, 25 Mar 2009 10:51:08 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 31C6F3A6D4A; Wed, 25 Mar 2009 10:50:13 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090325175049.GB6740@isi.edu> References: <20090325175049.GB6740@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14379 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 25 Mar 2009 10:50:14 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14379] AutoReply: Informational Independent Submission: draft-despres-6rd-02.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-despres-6rd-02.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14379]. Please include the string: [rt.amsl.com #14379] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-despres-6rd-02.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. IPv6 Rapid Deployment on IPv4 infrastructures (6rd) IPv6 rapid deployment (6rd) builds upon mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly deploy IPv6 unicast service to IPv4 sites to which it provides customer premise equipment. Like 6to4, it utilizes stateless IPv6 in IPv4 encapsulation in order to transit IPv4-only network infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 prefix of its own in place of the fixed 6to4 prefix. A service provider has used this mechanism for its own IPv6 "rapid deployment": five weeks from first exposure to 6rd principles to more than 1,500,000 residential sites being provided quasi-native IPv6, under the only condition that they activate it. Five week timeout expires on 29 April 2009. (Note that we have included an additional week because of the current IETF.) Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Wed Mar 25 11:05:00 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2PI3qKV020428 for ; Wed, 25 Mar 2009 11:03:52 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 50A153A6D56; Wed, 25 Mar 2009 11:02:59 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090325180313.GC6740@isi.edu> References: <20090325180313.GC6740@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14385 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 25 Mar 2009 11:02:59 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14385] AutoReply: Informational Independent Submission: draft-leung-mip4-proxy-mode-10.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-leung-mip4-proxy-mode-10.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14385]. Please include the string: [rt.amsl.com #14385] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Independent Independent Submission: draft-leung-mip4-proxy-mode-10.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. WiMAX Forum/3GPP2 Proxy Mobile IPv4 Mobile IPv4 is a standard mobility protocol that enables IPv4 device to move among networks while maintaining its IP address. The mobile device has the Mobile IPv4 client function to signal its location to the routing anchor, known as the Home Agent. However, there are many IPv4 devices without such capability due to various reasons. This document describes Proxy Mobile IPv4 (PMIPv4), a scheme based on having the Mobile IPv4 client function in a network entity to provide mobility support for an unaltered and mobility-unaware IPv4 device. This document also describes a particular application of PMIPv4 as specified in the WiMAX Forum and another application that is to be adopted in 3GPP2. Five week timeout expires on 29 April 2009. Note that we have included an additional week because of the current IETF. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Wed Mar 25 11:10:26 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2PI97C3023071 for ; Wed, 25 Mar 2009 11:09:07 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 1919C3A6B7D; Wed, 25 Mar 2009 11:08:13 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090325180808.GD6740@isi.edu> References: <20090325180313.GC6740@isi.edu> <20090325180808.GD6740@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14387 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 25 Mar 2009 11:08:14 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14387] AutoReply: Re: Informational Independent Submission: draft-leung-mip4-proxy-mode-10.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Informational Independent Submission: draft-leung-mip4-proxy-mode-10.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14387]. Please include the string: [rt.amsl.com #14387] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, Please disregard the message below. We have previously received your "no problem with publication" message on 15 September 2008. Sorry for the confusion! Thank you. RFC Editor On Wed, Mar 25, 2009 at 11:03:13AM -0700, RFC Editor wrote: > IESG, > > This document was submitted to the RFC Editor to be published as an > Independent Independent Submission: draft-leung-mip4-proxy-mode-10.txt > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > > WiMAX Forum/3GPP2 Proxy Mobile IPv4 > > Mobile IPv4 is a standard mobility protocol that enables IPv4 > device to move among networks while maintaining its IP address. > The mobile device has the Mobile IPv4 client function to signal its > location to the routing anchor, known as the Home Agent. However, > there are many IPv4 devices without such capability due to various > reasons. This document describes Proxy Mobile IPv4 (PMIPv4), a > scheme based on having the Mobile IPv4 client function in a network > entity to provide mobility support for an unaltered and > mobility-unaware IPv4 device. This document also describes a > particular application of PMIPv4 as specified in the WiMAX Forum > and another application that is to be adopted in 3GPP2. > > Five week timeout expires on 29 April 2009. > Note that we have included an additional week because of the current > IETF. > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents From wwwrun@core3.amsl.com Wed Mar 25 11:15:06 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2PIEjOM025712 for ; Wed, 25 Mar 2009 11:14:46 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E370D3A696F; Wed, 25 Mar 2009 11:13:52 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14385 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 25 Mar 2009 11:13:52 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14385] Resolved: Informational Independent Submission: draft-leung-mip4-proxy-mode-10.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu Mar 26 10:10:38 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2QH9qEb024714 for ; Thu, 26 Mar 2009 10:09:53 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 6E4DE28C0E4; Thu, 26 Mar 2009 10:08:58 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14379 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 26 Mar 2009 10:08:58 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14379] Resolved: Informational Independent Submission: draft-despres-6rd-02.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu Apr 2 14:27:11 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n32LQqLj015042 for ; Thu, 2 Apr 2009 14:26:53 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 8CAD73A6A53; Thu, 2 Apr 2009 14:25:50 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13912 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 02 Apr 2009 14:25:50 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13912] Resolved: Re: Author info change for three drafts in your queue According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu Apr 2 14:27:14 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n32LQkP8015010 for ; Thu, 2 Apr 2009 14:26:47 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C97A63A67AC; Thu, 2 Apr 2009 14:25:43 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090313160825.GD6570@isi.edu> References: <49ba7c46.47c1f10a.082b.ffffe863@mx.google.com> <20090313160825.GD6570@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13912 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 02 Apr 2009 14:25:43 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13912] Re: Author info change for three drafts in your queue Hi Tom (and RFC Editor), Your email address has been updated in our database. Best regards, Cindy On Fri Mar 13 09:09:05 2009, rfc-editor@rfc-editor.org wrote: > Hi Tom and IESG Secretariat*, > > Thanks for providing us with your updated email address. > > a) We have updated our database and the documents to reflect your new > address. However, when the documents reach AUTH48, we expect that you > may want to change your street address as well. > > b*) We are unsure whether there is an IETF author's database. We are > including the IETF Secretariat in this thread in the hopes that they > can provide you with that information. > > c) There is no issue with our processing the documents with/without > the RFC 5378 copyright at this time. You do not need to resubmit your > documents since they have already been approved for publication and > are in our queue. > > During the transition to the RFC 5378 copyright notice and legends, we > are updating the text with the new RFC 5378 copyright notice, and > including the optional 6.c.iii paragrph by default for I-Ds that were > submitted with the pre-RFC-5378 copyright. During AUTH48, you will > have the opportunity to tell us whether the optional 6.c.iii is not > necessary and can be deleted. > > Please let us know if you have any questions. > > Thanks! > > RFC Editor/sg > > > > On Fri, Mar 13, 2009 at 11:30:47AM -0400, Tom Talpey wrote: > > I am a co-author of three drafts from the NFSv4 working group > > which are in the editor's queue. I am, however, no longer at > > NetApp, to which the drafts and probably your database point. > > > > So, I'd like to: > > a) let you know my current best address (above), and > > b) ask whether there is some other registry I need to > > change - the IETF author's database? > > > > The drafts in question are: > > draft-ietf-nfsv4-nfs-rdma-problem-statement > > draft-ietf-nfsv4-rpcrdma > > draft-ietf-nfsv4-nfsdirect > > > > Oh, one other question perhaps. Of the three, only -rpcrdma uses > > the new RFC5378 assignment text. Is there any issue with the > > other two; should they be updated, or do they proceed as-is? > > > > The source for these three drafts is available on request. They've > > been in the works for a long time, so they are in nroff format. > > > > Tom. > From wwwrun@core3.amsl.com Tue Apr 28 09:26:34 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SGKaNS006748 for ; Tue, 28 Apr 2009 09:20:37 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E49FE28C0F6; Tue, 28 Apr 2009 09:19:13 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090428161656.GB1827@isi.edu> References: <20090428161656.GB1827@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14960 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 09:19:13 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14960] AutoReply: Informational Independent Submission: draft-templin-isatapv4-01.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-templin-isatapv4-01.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14960]. Please include the string: [rt.amsl.com #14960] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-templin-isatapv4-01.txt Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Transmission of IPv4 Packets over ISATAP Interfaces The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) specifies a Non-Broadcast, Multiple Access (NBMA) interface type for the transmission of IPv6 packets over IPv4 networks using automatic IPv6-in-IPv4 encapsulation. The original specifications make no provisions for the encapsulation and transmission of IPv4 packets, however. This document specifies a method for transmitting IPv4 packets over ISATAP interfaces. Four week timeout expires on 26 May 2009. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Tue Apr 28 09:35:23 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SGTYNW011957 for ; Tue, 28 Apr 2009 09:29:35 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C10AE3A6C33; Tue, 28 Apr 2009 09:28:12 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090428162242.GC1827@isi.edu> References: <20090428145552.30C3528C1D8@core3.amsl.com> <20090428162242.GC1827@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14961 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 09:28:12 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14961] AutoReply: Re: Protocol Action: 'Mobile IPv6 Support for Dual Stack Hosts and Routers' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Mobile IPv6 Support for Dual Stack Hosts and Routers' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14961]. Please include the string: [rt.amsl.com #14961] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Apr 28, 2009 at 07:55:52AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Mobile IPv6 Support for Dual Stack Hosts and Routers ' > as a Proposed Standard > > This document is the product of the Mobility EXTensions for IPv6 Working > Group. > > The IESG contact persons are Jari Arkko and Ralph Droms. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-v4traversal-10.txt > > Technical Summary > > The current Mobile IPv6 and NEMO specifications support IPv6 only. > This specification extends those standards to allow the registration > of IPv4 addresses and prefixes, respectively, and the transport of > both IPv4 and IPv6 packets over the tunnel to the home agent. This > specification also allows the Mobile Node to roam over both IPv6 and > IPv4, including the case where Network Address Translation is present > on the path between the mobile node and its home agent. > > Working Group Summary > > This document is a product of the Mobility EXTensions for IPv6 > (MEXT) working group. > > Document Quality > > Pasi Eronen reviewed the specification and his comments regarding > interaction of DSMIPv6 with the IPsec architecture were resolved. > > Personnel > > The Document Shepherd for this document is Julien Laganier > (MEXT WG co-chair). The Responsible Area Director is Jari Arkko > (Internet Area Director). > > RFC Editor Note > > Please add the following paragraph to the end of Section 5.4.4: > > This specification does not support mobile nodes returning home > while using IPv4. That is, the IPv4 support is only defined for > mobile nodes that are in a visited network. From wwwrun@core3.amsl.com Tue Apr 28 09:41:25 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SGZSIw015329 for ; Tue, 28 Apr 2009 09:35:29 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D8D663A703C; Tue, 28 Apr 2009 09:34:05 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14961 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 09:34:05 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14961] Resolved: Re: Protocol Action: 'Mobile IPv6 Support for Dual Stack Hosts and Routers' to Proposed Standard According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Apr 28 11:16:36 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on clone.isi.edu X-Spam-Level: X-Spam-Status: No, score=-4.1 required=5.0 tests=ANY_BOUNCE_MESSAGE,AWL, BAYES_00,RCVD_IN_DNSWL_MED,VBOUNCE_MESSAGE autolearn=ham version=3.2.4 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SI8Idv005367 for ; Tue, 28 Apr 2009 11:08:19 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 34BD928C282; Tue, 28 Apr 2009 11:06:45 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090428180053.GD1827@isi.edu> References: <20090428180053.GD1827@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14963 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 11:06:46 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14963] AutoReply: Informational Independent Submission: draft-brusilovsky-pak-09.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-brusilovsky-pak-09.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14963]. Please include the string: [rt.amsl.com #14963] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-brusilovsky-pak-09.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 26 May 2009. Password-Authenticated Diffie-Hellman Exchange (PAK) This document proposes to add mutual authentication, based on human-memorizable password, to the basic unauthenticated Diffie-Hellman key exchange. The proposed algorithm is called Password-authenticated Key exchange (PAK). PAK allows two parties to authenticate themselves while performing the Diffie-Hellman exchange. The protocol is secure against all passive and active attacks. In particular, it does not allow either type of attackers to obtain any information that would enable an off-line dictionary attack on the password. PAK provides Forward Secrecy. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Tue Apr 28 11:31:06 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SIKO26012909 for ; Tue, 28 Apr 2009 11:20:24 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E40A33A711E; Tue, 28 Apr 2009 11:19:01 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090428181041.GE1827@isi.edu> References: <20090428162054.D881728C0DC@core3.amsl.com> <20090428181041.GE1827@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14964 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 11:19:01 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14964] AutoReply: Re: Protocol Action: 'Internet Calendaring and Scheduling Core Object Specification (iCalendar)' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Internet Calendaring and Scheduling Core Object Specification (iCalendar)' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14964]. Please include the string: [rt.amsl.com #14964] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Apr 28, 2009 at 09:20:54AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Internet Calendaring and Scheduling Core Object Specification > (iCalendar) ' > as a Proposed Standard > > This document is the product of the Calendaring and Scheduling Standards > Simplification Working Group. > > The IESG contact persons are Lisa Dusseault and Alexey Melnikov. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-calsify-rfc2445bis-10.txt > > Technical Summary > > This document defines the iCalendar data format for representing and > exchanging calendaring and scheduling information such as events, > to-dos, journal entries and free/busy information, independent of any > particular calendar service or protocol. > > Working Group Summary > > The working group proceeded with the work in an orderly fashion, opening > tickets for all the found issues in the original RFC2445, and then > systematically closing them until no known issues remained. > > Document Quality > > There are a number of existing implementations of the original RFC2445 > specification that are likely to upgrade their implementation to the new > specification. > > During the process of developing this document, the CalConnect.org > industry consortium provided various types of vendor feedback and errata > over the original specification. > > The working group took special care to take into account this feedback > as well as the feedback received from a number of other contributors, > some of which are also mentioned in the document's Acknowledgements > section. > > Personnel > > Document Shepherd: Aki Niemi > > Responsible AD: Lisa Dusseault > > The IANA Expert(s) for the registries in this document are Cyrus Daboo > and Bernard Desruisseaux. > > > Note to RFC Editor > > Please ensure that the ABNF is valid, including semi-colons or explicit > spaces in empty lines within rules. > > OLD in section 3.2.19: > > The parameter MUST be specified on properties with a DATE-TIME > value if the DATE-TIME is not either a UTC or a "floating" time. > > NEW: > > The parameter MUST be specified on properties with a DATE-TIME > value if the DATE-TIME is not either a UTC or a "floating" time. > Failure to include and follow VTIMEZONE definitions in iCalendar > objects may lead to inconsistent understanding of the local time at any > given location. From wwwrun@core3.amsl.com Tue Apr 28 12:37:24 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SJWjX4021752 for ; Tue, 28 Apr 2009 12:32:45 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id A4E593A6D20; Tue, 28 Apr 2009 12:31:17 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14964 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 12:31:17 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14964] Resolved: Re: Protocol Action: 'Internet Calendaring and Scheduling Core Object Specification (iCalendar)' to Proposed Standard According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue Apr 28 13:15:40 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3SKE7gZ012096 for ; Tue, 28 Apr 2009 13:14:08 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 55CEA3A6960; Tue, 28 Apr 2009 13:12:44 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14963 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 28 Apr 2009 13:12:45 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14963] Resolved: Informational Independent Submission: draft-brusilovsky-pak-09.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 29 08:36:43 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3TFYHqj021996 for ; Wed, 29 Apr 2009 08:34:18 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 6B0D63A7144; Wed, 29 Apr 2009 08:32:54 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090429153136.GA11879@isi.edu> References: <20090428200907.7E8E93A6929@core3.amsl.com> <20090429153136.GA11879@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14993 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Apr 2009 08:32:54 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14993] AutoReply: Re: Protocol Action: 'BGP IPsec Tunnel Encapsulation Attribute' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'BGP IPsec Tunnel Encapsulation Attribute' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14993]. Please include the string: [rt.amsl.com #14993] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Apr 28, 2009 at 01:09:07PM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'BGP IPsec Tunnel Encapsulation Attribute ' > as a Proposed Standard > > This document is the product of the Softwires Working Group. > > The IESG contact persons are Ralph Droms and Jari Arkko. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-softwire-encaps-ipsec-03.txt > > Technical Summary > > The BGP Encapsulation Subsequence Address Family Identifiers (SAFI) > provides a method for the dynamic exchange of encapsulation > information, and the indication of encapsulation protocol types > to be used for different next hops. Currently support for GRE and L2TPv3 > tunnel types are defined. This document defines support for IPsec > tunnel types. > > > Working Group Summary > > The SOFTWIRE WG supports the development and advancement of this > document. > > > Protocol Quality > > This document was thoroughly reviewed by WG chairs and WG members, > including those with expertise in IPv4 to IPv6 transitions and > interworking. > > Dave Ward is the WG chair shepherd. Ralph Droms is the > responsible Area director. From wwwrun@core3.amsl.com Wed Apr 29 08:54:03 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3TFjtLj028099 for ; Wed, 29 Apr 2009 08:45:56 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id CE97528C2C6; Wed, 29 Apr 2009 08:44:32 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090429153845.GB11879@isi.edu> References: <20090429132440.8529128C1CC@core3.amsl.com> <20090429153845.GB11879@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14994 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Apr 2009 08:44:32 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14994] AutoReply: Re: Protocol Action: 'LDP Capabilities' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'LDP Capabilities' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14994]. Please include the string: [rt.amsl.com #14994] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Apr 29, 2009 at 06:24:40AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'LDP Capabilities ' > as a Proposed Standard > > This document is the product of the Multiprotocol Label Switching Working > Group. > > The IESG contact persons are Ross Callon and Adrian Farrel. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-capabilities-04.txt > > Technical Summary > > A number of enhancements to the Label Distribution Protocol (LDP) > have been proposed. Some have been implemented, and some are > advancing toward standardization. It is likely that additional > enhancements will be proposed in the future. At present, LDP has > no mechanism for advertising such enhancements at LDP session > initialization time. There is also no mechanism to enable and > disable enhancements after the session is established. This > document defines a mechanism for advertising LDP enhancements at > session initialization time, as well as a mechanism to enable and > disable enhancements after LDP session establishment. > > Working Group Summary > > This document represents the WG consensus as a whole: the WG as > a whole understands and agrees with it. The document has been > through wg last call with good and constructive comments, it has > also been reviewed by subject-matter experts who are WG members. > No controvery reported (see PROTO writeup by Loa Andersson in > the tracker) > > Document Quality > > There is at least one known implementation. The document has been > well reviewed in the WG and updated based on Gen-Art comments. > > Personnel > > Loa Andersson is the Document Shepherd for this document. Ross > Callon is the Responsible Area Director. > > RFC Editor Note > > The address and corporate affiliation for Bob Thomas should be > double checked. He can be contacted at: bobt727@yahoo.com. From wwwrun@core3.amsl.com Wed Apr 29 09:08:45 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3TFxgr4005207 for ; Wed, 29 Apr 2009 08:59:43 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0E1E73A6ECE; Wed, 29 Apr 2009 08:58:19 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14993 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Apr 2009 08:58:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14993] Resolved: Re: Protocol Action: 'BGP IPsec Tunnel Encapsulation Attribute' to Proposed Standard According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 29 09:12:33 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3TG0g9L005686 for ; Wed, 29 Apr 2009 09:00:43 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 18C5928C2B5; Wed, 29 Apr 2009 08:59:19 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14994 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Apr 2009 08:59:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14994] Resolved: Re: Protocol Action: 'LDP Capabilities' to Proposed Standard According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Wed Apr 29 09:18:03 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n3TG1wno006235 for ; Wed, 29 Apr 2009 09:01:58 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 76BBC28C2DE; Wed, 29 Apr 2009 09:00:34 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090429154822.GC11879@isi.edu> References: <20090429154822.GC11879@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #14995 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 29 Apr 2009 09:00:34 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #14995] AutoReply: [zeltsan@alcatel-lucent.com: RE: Informational Independent Submission: draft-brusilovsky-pak-09.txt] Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "[zeltsan@alcatel-lucent.com: RE: Informational Independent Submission: draft-brusilovsky-pak-09.txt]", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #14995]. Please include the string: [rt.amsl.com #14995] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, Please note that the authors notified us that version 10 is now available. Please review version 10. Thank you. RFC Editor ----- Forwarded message from "Zeltsan, Zachary (Zachary)" ----- Subject: RE: Informational Independent Submission: draft-brusilovsky-pak-09.txt Date: Wed, 29 Apr 2009 09:44:13 -0500 From: "Zeltsan, Zachary \(Zachary\)" To: "RFC Editor" , "IESG" , "iesg-secretary" Cc: "Brusilovsky, Alec \(Alec\)" , "Faynberg, Igor \(Igor\)" , , "Tim Polk" , "Ray Pelletier" , "Alfred HNnes" , "Jim Schaad" Dear RFC Editor, Please note that the latest version of the draft is -10. (http://tools.ietf.org/html/draft-brusilovsky-pak-10) With best regards, Zachary Zeltsan > -----Original Message----- > From: RFC Editor [mailto:rfc-editor@rfc-editor.org] > Sent: Tuesday, April 28, 2009 2:01 PM > To: IESG; iesg-secretary > Cc: RFC Editor; Brusilovsky, Alec (Alec); Faynberg, Igor > (Igor); sarvar@google.com; Zeltsan, Zachary (Zachary) > Subject: Informational Independent Submission: > draft-brusilovsky-pak-09.txt > > IESG, > > This document was submitted to the RFC Editor to be published > as an Informational Independent Submission: > draft-brusilovsky-pak-09.txt. > > Please let us know if this document conflicts with the IETF > standards process or other work being done in the IETF community. > > Four week timeout expires on 26 May 2009. > > > Password-Authenticated Diffie-Hellman Exchange (PAK) > > This document proposes to add mutual authentication, based on > human-memorizable password, to the basic unauthenticated > Diffie-Hellman key exchange. The proposed algorithm is called > Password-authenticated Key exchange (PAK). PAK allows two parties > to authenticate themselves while performing the Diffie-Hellman > exchange. > > The protocol is secure against all passive and active attacks. > In particular, it does not allow either type of attackers to obtain > any information that would enable an off-line dictionary attack on > the password. PAK provides Forward Secrecy. > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents > ----- End forwarded message ----- From wwwrun@core3.amsl.com Fri May 8 11:37:26 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n48IaICE016716 for ; Fri, 8 May 2009 11:36:19 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 68EBB3A6D9D; Fri, 8 May 2009 11:34:49 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090508183521.GC22575@isi.edu> References: <20090508183521.GC22575@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15133 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 08 May 2009 11:34:49 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15133] AutoReply: Informational Independent Submission: draft-ford-behave-top-06.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-ford-behave-top-06.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15133]. Please include the string: [rt.amsl.com #15133] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-ford-behave-top-06.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Unintended Consequence of two NAT deployments with Overlapping Address Space This document identifies two deployment scenarios that have arisen from the unconventional network topologies formed using Network Address Translator devices (NATs). First, the simplicity of administering networks through the combination of NAT and DHCP has increasingly lead to the deployment of multi-level inter-connected private networks involving overlapping private IP address spaces. Second, the proliferation of private networks in enterprises, hotels and conferences, and the wide spread use of Virtual Private Networks (VPNs) to access enterprise intranet from remote locations has increasingly lead to overlapping private IP address space between remote and corporate networks. The document does not dismiss these unconventional scenarios as invalid, but recognizes them as real and offers recommendations to help ensure these deployments can function without a meltdown. Four week timeout expires on 5 June 2009. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Fri May 8 16:14:51 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n48NDu31002056 for ; Fri, 8 May 2009 16:13:57 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 361E33A6B78; Fri, 8 May 2009 16:12:27 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15133 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 08 May 2009 16:12:27 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15133] Resolved: Informational Independent Submission: draft-ford-behave-top-06.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Thu May 14 15:35:25 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n4EMXJpj013183 for ; Thu, 14 May 2009 15:33:19 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 4271D28C35D; Thu, 14 May 2009 15:31:45 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090514223052.GA3014@isi.edu> References: <39C363776A4E8C4A94691D2BD9D1C9A105F06EF8@XCH-NW-7V2.nw.nos.boeing.com> <4A0C5F6B.1040009@piuha.net> <39C363776A4E8C4A94691D2BD9D1C9A105F06F42@XCH-NW-7V2.nw.nos.boeing.com> <4A0C6843.1060908@piuha.net> <20090514223052.GA3014@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15235 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 14 May 2009 15:31:45 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15235] AutoReply: Informational Indepenent Submission: draft-templin-seal-23.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Indepenent Submission: draft-templin-seal-23.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15235]. Please include the string: [rt.amsl.com #15235] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-templin-seal-23.txt. This document was previously submitted for IESG review for Experimental publication in August 2008. We are resumbitting this document for consideration as an Informational publication for the reasons Jari specifies in the message below. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Four week timeout expires on 11 May 2009. The Subnetwork Encapsulation and Adaptation Layer (SEAL) For the purpose of this document, subnetworks are defined as virtual topologies that span connected network regions bounded by encapsulating border nodes. These virtual topologies may span multiple IP and/or sub-IP layer forwarding hops, and can introduce failure modes due to packet duplication and/or links with diverse Maximum Transmission Units (MTUs). This document specifies a Subnetwork Encapsulation and Adaptation Layer (SEAL) that accommodates such virtual topologies over diverse underlying link technologies. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents On Thu, May 14, 2009 at 09:51:47PM +0300, Jari Arkko wrote: > All, > > I marked draft-templin-seal as something that we'll deal on the next > Thursday's IESG telechat. This draft has been in the RFC editor process > already, and had passed the IESG's RFC 3932 review some time ago. > > IESG: The draft is being brought back because Fred wants to change the > status from Exp to Inf. I think that is fine, but I think its fair to > ask from the whole IESG. My recommendation will be the same one that we > (or Mark) had for this the last time around. That is, I am in favor of > the publication. > > Fred: You have no extreme hurry with the document update. I said > originally that for the changes you wouldn't even have to bring them > changes back to the IESG. Its just the status change that needs a check. > But it would be good if you can get the new version in, say by Saturday. > If for some reason you find out that you need more time, just let us > know and we can take it off from the agenda. > > RFC Editor: given Fred's request, I have bypassed a bit of process here, > because normally the RFC Editor would come and ask the IESG for these > checks. This was done just to avoid an extra couple weeks of delay if > the document doesn't make to the agenda that goes out in few hours. You > could still send the formal request, or if you like, just record what > the state of the document is. I think we agree that status changes or > significant revision warrants a new check. The former was the case here. > > Jari From wwwrun@core3.amsl.com Thu May 14 16:03:55 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n4EN2veO024789 for ; Thu, 14 May 2009 16:02:58 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0E73A3A6911; Thu, 14 May 2009 16:01:23 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090514230110.GD3014@isi.edu> References: <20090514230110.GD3014@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15236 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Thu, 14 May 2009 16:01:24 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15236] AutoReply: Informational Independent Submission: draft-floyd-tcpm-ackcc-05.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Informational Independent Submission: draft-floyd-tcpm-ackcc-05.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15236]. Please include the string: [rt.amsl.com #15236] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, This document was submitted to the RFC Editor to be published as an Informational Independent Submission: draft-floyd-tcpm-ackcc-05.txt. Please let us know if this document conflicts with the IETF standards process or other work being done in the IETF community. Adding Acknowledgement Congestion Control to TCP This document describes a possible congestion control mechanism for acknowledgement traffic (ACKs) in TCP. The document specifies an end-to-end acknowledgement congestion control mechanism for TCP that uses participation from both TCP hosts, the TCP data sender and the TCP data receiver. The TCP data sender detects lost or ECN-marked ACK packets, and tells the TCP data receiver the ACK Ratio R to use to respond to the congestion on the reverse path from the data receiver to the data sender. The TCP data receiver sends roughly one ACK packet for every R data packets received. This mechanism is based on the acknowledgement congestion control in DCCP's CCID 2. This acknowledgement congestion control mechanism is being specified for further evaluation by the network community. Four week timeout expires on 11 June 2009. Sincerely, Sandy Ginoza - USC/ISI Request for Comments Documents From wwwrun@core3.amsl.com Fri May 15 08:59:43 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n4FFwsuC003672 for ; Fri, 15 May 2009 08:58:54 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 07BB13A6DB2; Fri, 15 May 2009 08:57:03 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15235 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 15 May 2009 08:57:04 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15235] Resolved: Informational Indepenent Submission: draft-templin-seal-23.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Fri May 15 09:16:58 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n4FGG22j011750 for ; Fri, 15 May 2009 09:16:02 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id F365728C221; Fri, 15 May 2009 09:14:27 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15236 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 15 May 2009 09:14:27 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15236] Resolved: Informational Independent Submission: draft-floyd-tcpm-ackcc-05.txt According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. From wwwrun@core3.amsl.com Tue May 26 15:05:01 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES, SUBJ_HAS_UNIQ_ID autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n4QM4VWg006907 for ; Tue, 26 May 2009 15:04:31 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id CB4013A6C9E; Tue, 26 May 2009 15:02:48 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #13888 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 26 May 2009 15:02:48 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #13888] Resolved: Re: [Fwd: New Version Notification - draft-lochter-pkix-brainpool-ecc-03.txt] We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Mon Jun 8 09:51:01 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n58GnuxY000027 for ; Mon, 8 Jun 2009 09:50:00 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D9DF73A6B3F; Mon, 8 Jun 2009 09:49:50 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090608164937.GD28803@isi.edu> References: <20090608150729.87E373A6DE0@core3.amsl.com> <20090608164937.GD28803@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15716 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 09:49:50 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15716] AutoReply: Re: Document Action: 'Lemonade Notifications Architecture' to Informational RFC Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Document Action: 'Lemonade Notifications Architecture' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15716]. Please include the string: [rt.amsl.com #15716] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Jun 08, 2009 at 08:07:29AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Lemonade Notifications Architecture ' > as an Informational RFC > > This document is the product of the Enhancements to Internet email to > Support Diverse Service Environments Working Group. > > The IESG contact persons are Alexey Melnikov and Lisa Dusseault. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-lemonade-notifications-10.txt > > Technical Summary > > This document discusses how to provide notification and filtering > mechanisms to mail stores to meet Lemonade goals. > > This document also discusses the use of server to server > notifications, and how server to server notifications fit into an > architecture which provides server to client notifications. > > Working Group Summary > > Nothing out of the ordinary happened in the WG to note. > > Document Quality > > As an Informative document, no issues with protocols or > implementations. > > RFC Editor Notes > > Please change the Absract to read: > OLD: > This document discusses how to provide notification and filtering > mechanisms to mail stores to meet Lemonade goals. > > NEW: > This document discusses how to provide notification and filtering > mechanisms to mail stores to meet the goals of the Lemonade > (Enhancements to Internet email to Support Diverse Service > Environments) Working Group. > > In Section 1, 1st paragraph: > OLD: > The lemonade work [LEMONADE-PROFILE] identified a need to provide > ^ > notification and filtering mechanisms for use with IMAP [IMAP]. > > NEW: > The Lemonade work [LEMONADE-PROFILE] identified a need to provide > ^ > notification and filtering mechanisms for use with IMAP [IMAP]. From wwwrun@core3.amsl.com Mon Jun 8 09:58:29 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n58GvmcO003421 for ; Mon, 8 Jun 2009 09:57:49 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 839083A6A14; Mon, 8 Jun 2009 09:57:42 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090608165145.GE28803@isi.edu> References: <20090608163305.1F8A53A6DB9@core3.amsl.com> <20090608165145.GE28803@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15717 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 09:57:42 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15717] AutoReply: Re: Protocol Action: 'GSS-API Extension for Storing Delegated Credentials' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'GSS-API Extension for Storing Delegated Credentials' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15717]. Please include the string: [rt.amsl.com #15717] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Jun 08, 2009 at 09:33:05AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'GSS-API Extension for Storing Delegated Credentials ' > as a Proposed Standard > > This document is the product of the Kitten (GSS-API Next Generation) > Working Group. > > The IESG contact persons are Tim Polk and Pasi Eronen. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-kitten-gssapi-store-cred-04.txt > > Technical Summary > > This document defines a new function for the GSS-API which allows > applications to store delegated (and other) credentials in the > implicit GSS-API credential store. This is needed for GSS-API > applications to use delegated credentials as they would use other > credentials. > > Working Group Summary > > This docment is a product of the kitten working group. The working > group process was uneventful. > > Document Quality > > There is at least 1 existing implementation of the feature and other > implementors are interested. > > Personnel > > Alexey Melnikov is the document shepherd for > this document. Tim Polk is the responsible AD. > > RFC Editor Note > > Please make the following changes: > > (1) In Section 3: > > OLD: > > o default_cred BOOLEAN -- if TRUE make the stored credential > available as the default credential (for acquisition with > GSS_C_NO_NAME as the desired name or for use as > GSS_C_NO_CREDENTIAL) > > > NEW: > > o default_cred BOOLEAN -- advisory input; if TRUE make the stored > credential available as the default credential (for acquisition > with GSS_C_NO_NAME as the desired name or for use as > GSS_C_NO_CREDENTIAL) > > (2) In Section 3: > > OLD: > > Finally, if the current credential store has no default credential > (that is, no credential that could be acquired for GSS_C_NO_NAME) or > if the default_cred input argument is TRUE, and the input credential > can be successfully stored, then the input credential will be > available for acquisition with GSS_C_NO_NAME as the desired name > input to GSS_Acquire_cred() or GSS_Add_cred() as well as for use as > GSS_C_NO_CREDENTIAL for the cred_handle inputs to GSS_Inquire_cred(), > GSS_Inquire_cred_by_mech(), GSS_Init_sec_context() and > GSS_Accept_sec_context(). > > > NEW: > > In the GSS-API the default credential can be used by using > GSS_C_NO_CREDENTIAL or a CREDENTIAL handle acquired by calling > GSS_Acquire_cred() or GSS_Add_cred() with the desired_name input set > to GSS_C_NO_NAME. > > If the default_cred input argument is TRUE, and the input credential > can be successfully stored, then the input credential SHOULD be > stored as the default credential (see above). > > If the current credential store has no default credential (see above) > then the implementation MAY make the stored credentials available as > the default credential regardless of the value of the default_cred > input argument. From wwwrun@core3.amsl.com Mon Jun 8 10:07:22 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n58H6Lbb007337 for ; Mon, 8 Jun 2009 10:06:22 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 798033A6B64; Mon, 8 Jun 2009 10:06:15 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090608170308.GF28803@isi.edu> References: <20090608163756.EA3C83A6D02@core3.amsl.com> <20090608170308.GF28803@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15718 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 10:06:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15718] AutoReply: Re: Protocol Action: 'Extended Generic Security Service Mechanism Inquiry APIs' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Extended Generic Security Service Mechanism Inquiry APIs' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15718]. Please include the string: [rt.amsl.com #15718] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Jun 08, 2009 at 09:37:56AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Extended Generic Security Service Mechanism Inquiry APIs ' > as a Proposed Standard > > This document is the product of the Kitten (GSS-API Next Generation) > Working Group. > > The IESG contact persons are Tim Polk and Pasi Eronen. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-kitten-extended-mech-inquiry-06.txt > > Technical Summary > > This document introduces new application programming interfaces > (APIs) to the Generic Security Services API (GSS-API) for extended > mechanism attribute inquiry. > > This document provides new functionality to obtain specific GSS-API > mechanism attributes. It defines new GSS-API functions that allow > retrieval and display of said attributes. These interfaces are primarily > intended to reduce instances of hardcoding of mechanism identifiers > in GSS applications. > > Working Group Summary > > The WG process was not controversial. > > Document Quality > > There are no implementors of these interfaces that we know of. However, > there should be significant demand once these interfaces become > standard, as a number of applications have hard-coded around limitations > of the current GSS-API. Enabling better programming practices is desired. > > Personnel > > Shawn M. Emery is the document shepherd for this > document. Tim Polk is the responsible AD. > > RFC Editor Note > > Please make the following six changes: > > (1) Section 3.4.2, title: > > s/3.4.2. GSS_Indicate_mechs_by_attr()/3.4.2. > GSS_Indicate_mechs_by_attrs()/ > > (2) Section 3.4.3, last sentence: > > s/GSS_Inquire_mech_attrs_for_mech()/GSS_Inquire_attrs_for_mech() > > (3) Section 3.4.6, third sentence: > > s/typdefs/typedefs/ > > (4) Section 3.4.6, Figure 2 > > OLD: > OM_uint32 gss_inquire_mechs_for_attrs( > OM_uint32 *minor_status, > gss_const_OID_set desired_mech_attrs, > gss_const_OID_set except_mech_attrs, > gss_const_OID_set critical_mech_attrs, > gss_OID_set *mechs); > NEW: > OM_uint32 gss_indicate_mechs_by_attrs( > OM_uint32 *minor_status, > gss_const_OID_set desired_mech_attrs, > gss_const_OID_set except_mech_attrs, > gss_const_OID_set critical_mech_attrs, > gss_OID_set *mechs); > > (5) Section 5, first sentence: > > s/namsepace/namespace/ > > (6) Section 5, first sentence: > > s/IESG Protocol Action/IETF Consensus/ From wwwrun@core3.amsl.com Mon Jun 8 11:08:57 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n58I8SMk028096 for ; Mon, 8 Jun 2009 11:08:28 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 539A03A6DCA; Mon, 8 Jun 2009 11:08:22 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15716 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 11:08:22 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15716] Resolved: Re: Document Action: 'Lemonade Notifications Architecture' to Informational RFC We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Mon Jun 8 11:09:27 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n58I8v6j028242 for ; Mon, 8 Jun 2009 11:08:58 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id F3BC53A6DD9; Mon, 8 Jun 2009 11:08:51 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15717 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 11:08:51 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15717] Resolved: Re: Protocol Action: 'GSS-API Extension for Storing Delegated Credentials' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Mon Jun 8 11:10:36 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n58I9kNp028470 for ; Mon, 8 Jun 2009 11:09:47 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 8A8573A69E3; Mon, 8 Jun 2009 11:09:40 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15718 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 11:09:40 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15718] Resolved: Re: Protocol Action: 'Extended Generic Security Service Mechanism Inquiry APIs' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Mon Jun 8 17:04:29 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n59031vX023431 for ; Mon, 8 Jun 2009 17:03:02 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 4188028C161; Mon, 8 Jun 2009 17:02:54 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090609000205.GM28803@isi.edu> References: <20090608172139.83AFD3A6878@core3.amsl.com> <20090609000205.GM28803@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15732 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 17:02:55 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15732] AutoReply: Re: Document Action: 'Implications of 'retransmission-allowed' for SIP Location Conveyance' to Informational RFC Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Document Action: 'Implications of 'retransmission-allowed' for SIP Location Conveyance' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15732]. Please include the string: [rt.amsl.com #15732] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Jun 08, 2009 at 10:21:39AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Implications of 'retransmission-allowed' for SIP Location Conveyance ' > as an Informational RFC > > This document is the product of the Geographic Location/Privacy Working > Group. > > The IESG contact persons are Cullen Jennings and Robert Sparks. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-geopriv-sip-lo-retransmission-02.txt > > Technical Summary > > This document explores an ambiguity in the interpretation of the > element of the Presence Information Data Format > for Location Objects (PIDF-LO) in cases where PIDF-LO is conveyed by the > Session Initiation Protocol (SIP). It provides recommendations for how > the SIP location conveyance mechanism should adapt to this ambiguity. > > Working Group Summary > > This document was produced in order to express the consensus of the > GEOPRIV working group on a privacy issue raised by location conveyance > in the SIP protocol. There is thus strong consensus within GEOPRIV > around the core privacy recommendations in the document. > > Document Quality > > The document has been reviewed by key participants from the GEOPRIV, > SIP, and privacy community, and its recommendations have been > implemented in draft-ietf-sip-location-conveyance-13. > > Personnel > > Document Shepherd is Richard Barnes. > > RFC Editor Note > > > At the end of first paragraph of the Abstract > OLD: > these ambiguities > NEW: > this ambiguity From wwwrun@core3.amsl.com Mon Jun 8 17:21:18 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n590I2fg029204 for ; Mon, 8 Jun 2009 17:18:03 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C57503A6C08; Mon, 8 Jun 2009 17:17:56 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090609001654.GN28803@isi.edu> References: <20090608225919.93D5E3A6C6A@core3.amsl.com> <20090609001654.GN28803@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15733 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 08 Jun 2009 17:17:56 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15733] AutoReply: Re: Document Action: 'Internet Mail Architecture' to Informational RFC Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Document Action: 'Internet Mail Architecture' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #15733]. Please include the string: [rt.amsl.com #15733] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Jun 08, 2009 at 03:59:19PM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Internet Mail Architecture ' > as an Informational RFC > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Alexey Melnikov. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-crocker-email-arch-14.txt > > Technical Summary > > Public discussion of the Internet Mail service often lacks > common terminology and a common frame of reference for these > components and their activities. Having a common reference > model and terminology makes a basic difference when talking > about problems with the service, changes in policy, or > enhancement to the service's functionality. This document > offers an enhanced Internet Mail architecture that targets > description of the existing service, in order to facilitate > clearer and more efficient technical, operations and policy > discussions about email. > > Working Group Summary > > This document was discussed within the mail community on the > mailing lists dedicated to SMTP and the Mail Format. Some of the > terms came about as a compromise after long discussions, but > rough consensus was achieved on all points. Members of the > working groups dealing with IMAP and LEMONADE were aware of this > effort, but it was not an appropriate topic for those working > groups to place on their charters. There is no other current > working group dealing with the mail system in general. > > Document Quality > > This document does not create a protocol specification. > > The acknowledgments indicate that Graham Klyne, Pete Resnick > and Steve Atkins provided thoughtful insight on the framework > and details of the original drafts. A number of other people > have provided additional reviews and insights. > > Personnel > > Who is the Document Shepherd for this document? Tony Hansen > Who is the Responsible Area Director? Chris Newman and Alexey Melnikov > have reviewed this document for IESG. > > > RFC Editor Note > > Please replace [RFC3685] with [RFC5235]. > > In Section 3.4.1, 2nd paragraph, 1st sentence: > OLD: > Message-ID: is be globally unique. > ^^ > NEW: > Message-ID: is globally unique. > ^ From wwwrun@core3.amsl.com Tue Jun 9 06:50:51 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n59DnQIU029500 for ; Tue, 9 Jun 2009 06:49:27 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 27C693A6912; Tue, 9 Jun 2009 06:49:19 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15732 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 09 Jun 2009 06:49:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15732] Resolved: Re: Document Action: 'Implications of 'retransmission-allowed' for SIP Location Conveyance' to Informational RFC We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Tue Jun 9 06:51:44 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SUBJ_HAS_SPACES autolearn=no version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n59DoSMc029929 for ; Tue, 9 Jun 2009 06:50:29 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D29803A6856; Tue, 9 Jun 2009 06:50:18 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #15733 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 09 Jun 2009 06:50:18 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #15733] Resolved: Re: Document Action: 'Internet Mail Architecture' to Informational RFC We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Mon Jun 29 17:09:24 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n5U08kDR008139 for ; Mon, 29 Jun 2009 17:08:47 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0B28328C181; Mon, 29 Jun 2009 17:08:24 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090630000706.GD13898@isi.edu> References: <9abf48a60906271119h59ed4472o7a0ac7d0b80b8394@mail.gmail.com> <20090630000706.GD13898@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16291 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Mon, 29 Jun 2009 17:08:25 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #16291] AutoReply: Re: What happened to draft-irtf-asrg-dnsbl ? Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: What happened to draft-irtf-asrg-dnsbl ?", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #16291]. Please include the string: [rt.amsl.com #16291] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have received an inquiry about the state of , and I'm hoping you can help me sort this out. The I-D tracker lists the state as "Approved-announcement sent." However, we do not believe we have received a document action for this I-D. The comment log lists the additional action after "Approved-announcement sent": State Changes to IESG Evaluation from Approved-announcement to be sent by system The above entry has the same entry date as "Approved-anouncement sent." Could you please check the state of this document and (re)send the document action as necessary? Please let me know if you have questions. Thanks! Sandy On Sat, Jun 27, 2009 at 02:19:52PM -0400, Barry Leiba wrote: > Hi, Aaron, RFC Editor, > What ever happened to > https://datatracker.ietf.org/idtracker/draft-irtf-asrg-dnsbl/ > after all the discussion? The tracker says the state went to > "approved, announcement sent" in December, but I don't see it in the > RFC list nor in the RFC Editor queue. What did I miss? > > Barry > -- > Barry Leiba (barryleiba@computer.org) > http://internetmessagingtechnology.org/ From wwwrun@core3.amsl.com Tue Jun 30 06:38:48 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n5UDbhvB015978 for ; Tue, 30 Jun 2009 06:37:44 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 49F533A6B16; Tue, 30 Jun 2009 06:37:19 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090630000706.GD13898@isi.edu> References: <9abf48a60906271119h59ed4472o7a0ac7d0b80b8394@mail.gmail.com> <20090630000706.GD13898@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16291 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 30 Jun 2009 06:37:19 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #16291] Re: What happened to draft-irtf-asrg-dnsbl ? Hi Sandy, As this is an IRTF document, that question is for them. The IESG discussed this document at the end of 2008, and it was approved as the IESG had "No Problem" with the IRTF publishing it. The message went back to the IRTF (via the IRSG) with a copy to the IETF-Announce list. As far as what happens next, I am assuming the IRTF takes it from there with the decision to publish it or not, and when, in the process, to get the RFC Editor involved. The Secretariat procedures for IRTF documents was changed last year, so we do not send the messages to the RFC Editor, and it was requested that we not cc the RFC Editor on the messages, either. You may view the message here: http://www.ietf.org/mail-archive/web/ietf-announce/current/msg05534.html I would think this person should query Aaron Falk as the IRTF Chair to find out what is going on with the document (or perhaps the asrg research group). Thanks! Amy On Mon Jun 29 17:08:24 2009, rfc-editor@rfc-editor.org wrote: > Greetings, > > We have received an inquiry about the state of > , and I'm hoping you can help me sort this out. > The I-D tracker lists the state as "Approved-announcement sent." > However, we do not believe we have received a document action for this > I-D. The comment log lists the additional action after > "Approved-announcement sent": > > State Changes to IESG Evaluation from Approved-announcement to be > sent by system > > The above entry has the same entry date as "Approved-anouncement > sent." Could you please check the state of this document and (re)send > the document action as necessary? > > Please let me know if you have questions. > > Thanks! > Sandy > > On Sat, Jun 27, 2009 at 02:19:52PM -0400, Barry Leiba wrote: > > Hi, Aaron, RFC Editor, > > What ever happened to > > https://datatracker.ietf.org/idtracker/draft-irtf-asrg-dnsbl/ > > after all the discussion? The tracker says the state went to > > "approved, announcement sent" in December, but I don't see it in the > > RFC list nor in the RFC Editor queue. What did I miss? > > > > Barry > > -- > > Barry Leiba (barryleiba@computer.org) > > http://internetmessagingtechnology.org/ > From wwwrun@core3.amsl.com Tue Jun 30 09:15:30 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n5UGEmKm017537 for ; Tue, 30 Jun 2009 09:14:49 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D3EC03A6BB2; Tue, 30 Jun 2009 09:14:26 -0700 (PDT) Subject: Re: [rt.amsl.com #16291] Re: What happened to draft-irtf-asrg-dnsbl ? From: "RFC Editor via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090630161302.GA25609@isi.edu> References: <9abf48a60906271119h59ed4472o7a0ac7d0b80b8394@mail.gmail.com> <20090630000706.GD13898@isi.edu> <20090630161302.GA25609@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16291 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 30 Jun 2009 09:14:26 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Hi Amy! Thanks, I will check with Aaron. I thought that when the I-D tracker indicated "approved-announcement sent" that it meant that a message had been sent to the RFC Editor. I didn't realize that that state is used to signify that an approved message was sent to other bodies. Good to know that we didn't have a disconnect!! Thanks for the info; it's a big help! As a side note, it would be great if the I-D tracker and the announcement messages could be updated to treat the IRTF documents as their own stream (as defined by RFC 4844), as they are not Independent submissions and they are no longer treated as such. Maybe this is something the secretariat could look into after is published as an RFC (it's in our queue waiting for 3932bis to be approved), as the following text could then point to the published RFC: The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thanks for your help and your consideration! Sandy On Tue, Jun 30, 2009 at 06:37:19AM -0700, Amy Vezza via RT wrote: > Hi Sandy, > > As this is an IRTF document, that question is for them. The IESG > discussed this document at the end of 2008, and it was approved as the > IESG had "No Problem" with the IRTF publishing it. The message went > back to the IRTF (via the IRSG) with a copy to the IETF-Announce list. > As far as what happens next, I am assuming the IRTF takes it from there > with the decision to publish it or not, and when, in the process, to get > the RFC Editor involved. > > The Secretariat procedures for IRTF documents was changed last year, so > we do not send the messages to the RFC Editor, and it was requested that > we not cc the RFC Editor on the messages, either. You may view the > message here: > > http://www.ietf.org/mail-archive/web/ietf-announce/current/msg05534.html > > I would think this person should query Aaron Falk as the IRTF Chair to > find out what is going on with the document (or perhaps the asrg > research group). > > Thanks! > > Amy > > On Mon Jun 29 17:08:24 2009, rfc-editor@rfc-editor.org wrote: > > Greetings, > > > > We have received an inquiry about the state of > > , and I'm hoping you can help me sort this out. > > The I-D tracker lists the state as "Approved-announcement sent." > > However, we do not believe we have received a document action for this > > I-D. The comment log lists the additional action after > > "Approved-announcement sent": > > > > State Changes to IESG Evaluation from Approved-announcement to be > > sent by system > > > > The above entry has the same entry date as "Approved-anouncement > > sent." Could you please check the state of this document and (re)send > > the document action as necessary? > > > > Please let me know if you have questions. > > > > Thanks! > > Sandy > > > > On Sat, Jun 27, 2009 at 02:19:52PM -0400, Barry Leiba wrote: > > > Hi, Aaron, RFC Editor, > > > What ever happened to > > > https://datatracker.ietf.org/idtracker/draft-irtf-asrg-dnsbl/ > > > after all the discussion? The tracker says the state went to > > > "approved, announcement sent" in December, but I don't see it in the > > > RFC list nor in the RFC Editor queue. What did I miss? > > > > > > Barry > > > -- > > > Barry Leiba (barryleiba@computer.org) > > > http://internetmessagingtechnology.org/ > > > > From wwwrun@core3.amsl.com Tue Jun 30 15:44:53 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n5UMhbQA005641 for ; Tue, 30 Jun 2009 15:43:37 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 4AA6D3A68CF; Tue, 30 Jun 2009 15:43:14 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090630224225.GC25609@isi.edu> References: <20090629162841.9EF0B28C27B@core3.amsl.com> <20090630224225.GC25609@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16354 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 30 Jun 2009 15:43:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #16354] AutoReply: Re: Protocol Action: 'Softwire Security Analysis and Requirements' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Softwire Security Analysis and Requirements' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #16354]. Please include the string: [rt.amsl.com #16354] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Jun 29, 2009 at 09:28:41AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Softwire Security Analysis and Requirements ' > as a Proposed Standard > > This document is the product of the Softwires Working Group. > > The IESG contact persons are Ralph Droms and Jari Arkko. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-softwire-security-requirements-09.txt > > Technical Summary > > This document describes the security guidelines for the softwire > "Hubs and Spokes" and "Mesh" solutions. Together with the discussion of > the softwire deployment scenarios, the vulnerability to the security > attacks is analyzed to provide the security protection mechanism such as > authentication, integrity and confidentiality to the softwire > control and data packets. > > Working Group Summary > > The SOFTWIRE WG supports the development and advancement of this > document. > > Protocol Quality > > This document was thoroughly reviewed by WG chairs and WG members, > including those with expertise in security, IPv4 to IPv6 > transitions and interworking. From wwwrun@core3.amsl.com Wed Jul 1 08:11:18 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n61FABOK024787 for ; Wed, 1 Jul 2009 08:10:11 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id A08103A683F; Wed, 1 Jul 2009 08:09:48 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16354 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 01 Jul 2009 08:09:48 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #16354] Resolved: Re: Protocol Action: 'Softwire Security Analysis and Requirements' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Tue Jul 7 15:12:51 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n67MCMBM023574 for ; Tue, 7 Jul 2009 15:12:23 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 076A928C2C5; Tue, 7 Jul 2009 15:11:55 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090707221054.GI21503@isi.edu> References: <20090707215624.272B63A6EAD@core3.amsl.com> <20090707221054.GI21503@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16547 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 07 Jul 2009 15:11:56 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #16547] AutoReply: Re: draft-ietf-smime-3278bis Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: draft-ietf-smime-3278bis", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #16547]. Please include the string: [rt.amsl.com #16547] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings IESG Secretary, Thanks for bringing this to our attention! It turns out that we must have missed it somehow! The document is being added now! Thanks, RFC Editor On Tue, Jul 07, 2009 at 02:56:24PM -0700, IESG Secretary wrote: > Hello! > > We wanted to check in with you folks about the state of > draft-ietf-smime-3278bis. The IESG approved this document, and the > announcement was sent out on June 8, 2009, but the document has not > appeared in the RFC Editor queue yet. > > For reference, the text of the approval announcement is copied below. > > Best regards, > IESG Secretary > > ----- > From: The IESG > To: IETF-Announce > Reply-to: iesg-secretary@ietf.org > Subject: Document Action: 'Use of Elliptic Curve Cryptography (ECC) > Algorithms in Cryptographic Message Syntax (CMS)' to Informational RFC > > The IESG has approved the following document: > > - 'Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic > Message Syntax (CMS) ' > as an Informational RFC > > This document is the product of the S/MIME Mail Security Working Group. > > The IESG contact persons are Tim Polk and Pasi Eronen. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-smime-3278bis-09.txt > > Technical Summary > > This document describes how to use Elliptic Curve Cryptography > (ECC) public-key algorithms in the Cryptographic Message Syntax (CMS). > The ECC algorithms support the creation of digital signatures and the > exchange of keys to encrypt or authenticate content. The definition of > the algorithm processing is based on the NIST FIPS 186-3 for digital > signatures, NIST SP800-56A and SEC1 for key agreement, RFC 3370 and > RFC 3565 for key wrap and content encryption, NIST FIPS 180-3 for > message digest, SEC1 for key derivation, and RFC 2104 and RFC 4231 > for message authentication code standards. This document > obsoletes RFC 3278. > > Working Group Summary > > This document was discussed on the S/MIME WG mailing list. The discussion > was primarily about document quality and consistency. > > Document Quality > > Implementations of SignedData with ECDSA and EnvelopedData with ECDH > have been available for some time from multiple vendors. Implementation > of the "new" algorithms (i.e., using SHA-2 and AES algorithms) is expected > > shortly, now that the relevant NIST documents (e.g., FIPS 186-3) have been > > finalized. > > Personnel > > Russ Housley is the document PROTO Shepherd. Tim Polk is the responsible > Security Area AD. From wwwrun@core3.amsl.com Tue Jul 7 15:59:37 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n67MwVUq009612 for ; Tue, 7 Jul 2009 15:58:31 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id E05D93A6E3D; Tue, 7 Jul 2009 15:58:03 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #16547 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 07 Jul 2009 15:58:03 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #16547] Resolved: Re: draft-ietf-smime-3278bis We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Fri Aug 14 09:34:09 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n7EGXkd5001420 for ; Fri, 14 Aug 2009 09:33:47 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 0FB6828C17A; Fri, 14 Aug 2009 09:33:41 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090814163311.GB17212@isi.edu> References: <20090508183521.GC22575@isi.edu> <20090814163311.GB17212@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #17979 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 14 Aug 2009 09:33:42 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #17979] AutoReply: Re: Informational Independent Submission: draft-ford-behave-top-07.txt Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Informational Independent Submission: draft-ford-behave-top-07.txt", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #17979]. Please include the string: [rt.amsl.com #17979] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- IESG, draft-ford-behave-top-06 was submitted for a RFC 3932 review on 8 May 2009. Please note that the authors have submitted -07 is now available at http://www.rfc-editor.org/internet-drafts/draft-ford-behave-top-07.txt. The authors have made updates in respone to comments from Ralph and and Cullen. Please review the new version and let us know the results of your RFC 3932 review. Thank you. Sandy On Fri, May 08, 2009 at 11:35:22AM -0700, RFC Editor wrote: > IESG, > > This document was submitted to the RFC Editor to be published as an > Informational Independent Submission: draft-ford-behave-top-06.txt. > > Please let us know if this document conflicts with the IETF standards > process or other work being done in the IETF community. > > > Unintended Consequence of two NAT deployments with > Overlapping Address Space > > This document identifies two deployment scenarios that have arisen > from the unconventional network topologies formed using Network > Address Translator devices (NATs). First, the simplicity of > administering networks through the combination of NAT and DHCP has > increasingly lead to the deployment of multi-level inter-connected > private networks involving overlapping private IP address spaces. > Second, the proliferation of private networks in enterprises, > hotels and conferences, and the wide spread use of Virtual Private > Networks (VPNs) to access enterprise intranet from remote locations > has increasingly lead to overlapping private IP address space > between remote and corporate networks. The document does not > dismiss these unconventional scenarios as invalid, but recognizes > them as real and offers recommendations to help ensure these > deployments can function without a meltdown. > > > Four week timeout expires on 5 June 2009. > > > Sincerely, > > Sandy Ginoza - USC/ISI > Request for Comments Documents From wwwrun@core3.amsl.com Tue Aug 25 12:14:00 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n7PJDQZR023194 for ; Tue, 25 Aug 2009 12:13:27 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 76F1A3A6AFB; Tue, 25 Aug 2009 12:13:18 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090825191245.GC25850@isi.edu> References: <20090825191245.GC25850@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18282 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 25 Aug 2009 12:13:19 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18282] AutoReply: New RFCs online Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "New RFCs online", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18282]. Please include the string: [rt.amsl.com #18282] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Hi All, Just a heads up that we have recently put RFCs 11, 109, 110, and 199 online. Russ (awhile back) had asked that we notify you when we're putting old documents online because a manual update may be necessary on the IETF site. Please let us know if you have any questions! Thanks! Sandy From wwwrun@core3.amsl.com Wed Aug 26 08:59:09 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n7QFwbAv007508 for ; Wed, 26 Aug 2009 08:58:38 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 85EBA3A70AC; Wed, 26 Aug 2009 08:57:36 -0700 (PDT) From: "Cindy Morgan via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18282 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: cmorgan@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 26 Aug 2009 08:57:36 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18282] Resolved: New RFCs online We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Fri Aug 28 13:45:55 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n7SKjC8c012401 for ; Fri, 28 Aug 2009 13:45:13 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 892A228C2E9; Fri, 28 Aug 2009 13:45:04 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090828204439.42FA7311525@bosco.isi.edu> References: <20090828204439.42FA7311525@bosco.isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18355 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Fri, 28 Aug 2009 13:45:04 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18355] AutoReply: Re: Regarding draft-iana-rfc3330bis Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Regarding draft-iana-rfc3330bis", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18355]. Please include the string: [rt.amsl.com #18355] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, Thank you for letting us know. These 3 documents will be published simultaneously. They are listed as a cluster: http://www.rfc-editor.org/cluster_info.php?cid=C46 RFC Editor/ah On Aug 28, 2009, at 1:57 PM, IESG Secretary wrote: > draft-iana-rfc3330bis-11.txt contains references to these two I-Ds: > > [I-D.iana-ipv4-examples] > Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks > Reserved for Documentation", draft-iana-ipv4-examples-01 > (work in progress), June 2009. > > [I-D.iana-special-ipv4-registry] > Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special > Purpose Address Registry", > draft-iana-special-ipv4-registry-01 (work in progress), > February 2009. > > Please publish all three of these documents as RFCs at the same time. From wwwrun@core3.amsl.com Tue Sep 1 16:05:40 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81N4c1L024631 for ; Tue, 1 Sep 2009 16:04:39 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 183A03A6E0A; Tue, 1 Sep 2009 16:04:23 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230409.GD13142@isi.edu> References: <20090805140150.40D463A6BF9@core3.amsl.com> <20090901230409.GD13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18420 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:04:24 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18420] AutoReply: Re: Protocol Action: 'Multiple Care-of Addresses Registration' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Multiple Care-of Addresses Registration' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18420]. Please include the string: [rt.amsl.com #18420] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Wed, Aug 05, 2009 at 07:01:50AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Multiple Care-of Addresses Registration ' > as a Proposed Standard > > > This document is the product of the Mobility EXTensions for IPv6 Working Group. > > The IESG contact persons are Jari Arkko and Ralph Droms. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-monami6-multiplecoa-14.txt > > Technical Summary > > According to the current Mobile IPv6 specification, a mobile node may > have several care-of addresses, but only one, called the primary > care-of address, that can be registered with its home agent and the > correspondent nodes. However, for matters of cost, bandwidth, delay, > etc, it is useful for the mobile node to get Internet access through > multiple accesses simultaneously, in which case the mobile node would > be configured with multiple active IPv6 care-of addresses. This > document proposes extensions to the Mobile IPv6 protocol to register > and use multiple care-of addresses. The extensions proposed in this > document can be used by Mobile Routers using the NEMO (Network > Mobility) Basic Support protocol as well. > > Working Group Summary > > This is a product of the former MONAMI6 WG, now part of MEXT WG. > > Document Quality > > There are 3 implementations of the protocol: An implementation > for MIPL (LINUX), more information: > http://www.nautilus6.org/implementation/index.php > http://software.nautilus6.org/MCoA/ > One implementation for BSD called SHISA which is part of WIDE > and is being maintained. Another implementation KDDI R&D. > > Interoperability between KDDI and SHISA in 2005. > http://www.ietf.org/proceedings/05nov/slides/monami6-8.pdf > > This feature is a must for the automotive industry > standardization effort made at ISO. > > There were many reviewers of the document, but especial > in depth reviews were provided by George Tsirtsis, Chan-Wah > Ng and Benjamin Lim. > > No MIB review nor media type reviews were needed. > > Personnel > > The Document Shepherd is Marcelo Bagnulo, and the AD is Jari > Arkko. From wwwrun@core3.amsl.com Tue Sep 1 16:15:06 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEapK028419 for ; Tue, 1 Sep 2009 16:14:37 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 88EEE3A6F40; Tue, 1 Sep 2009 16:14:21 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230458.GF13142@isi.edu> References: <20090831154530.B51E028C2E2@core3.amsl.com> <20090901230458.GF13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18426 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:21 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18426] AutoReply: Re: Protocol Action: 'Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18426]. Please include the string: [rt.amsl.com #18426] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Aug 31, 2009 at 08:45:30AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Mapping Simple Network Management Protocol (SNMP) Notifications to > SYSLOG Messages ' > as a Proposed Standard > > > This document is the product of the Operations and Management Area Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-snmp-05.txt > > Technical Summary > > This memo defines a mapping from Simple Network Management Protocol > (SNMP) notifications to SYSLOG messages. > > Working Group Summary > > There was consensus in the working group to publish this document. > > Document Quality > > SYSLOG and SNMP are widely implemented and deployed. The document was > reviewed in the Working Group and by the MIB DOctors. > > Personnel > > Scott Bradner is the Document Shepherd. Dan Romascanu is the > Responsible Area Director. From wwwrun@core3.amsl.com Tue Sep 1 16:15:10 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEZIg028416 for ; Tue, 1 Sep 2009 16:14:36 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 225AB3A6E9A; Tue, 1 Sep 2009 16:14:21 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230446.GE13142@isi.edu> References: <20090831153935.4252628C30F@core3.amsl.com> <20090901230446.GE13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18427 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:22 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18427] AutoReply: Re: Protocol Action: 'Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18427]. Please include the string: [rt.amsl.com #18427] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Aug 31, 2009 at 08:39:35AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Definitions of Managed Objects for Mapping SYSLOG Messages to Simple > Network Management Protocol (SNMP) Notifications ' > as a Proposed Standard > > > This document is the product of the Operations and Management Area Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-msg-mib-06.txt > > Technical Summary > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > In particular, it defines a mapping of SYSLOG messages to Simple > Network Management Protocol (SNMP) notifications. > > Working Group Summary > > There was consensus in the working group to publish these documents. > > Document Quality > > SNMP and SYSLOG are widely used and deployed. The document was > reviewed in the Working Group and by MIB DOctors. > > Personnel > > Scott Bradner is the Document Shepherd. Dan Romascanu is the > Responsible Area Director. From wwwrun@core3.amsl.com Tue Sep 1 16:15:12 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEZs6028397 for ; Tue, 1 Sep 2009 16:14:35 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 409F93A6CB2; Tue, 1 Sep 2009 16:14:19 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230543.GI13142@isi.edu> References: <20090831173337.2E41F28C209@core3.amsl.com> <20090901230543.GI13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18422 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18422] AutoReply: Re: Protocol Action: 'Extended MKCOL for WebDAV' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Extended MKCOL for WebDAV' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18422]. Please include the string: [rt.amsl.com #18422] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Aug 31, 2009 at 10:33:37AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Extended MKCOL for WebDAV ' > as a Proposed Standard > > > This document is the product of the vCard and CardDAV Working Group. > > The IESG contact persons are Alexey Melnikov and Lisa Dusseault. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-vcarddav-webdav-mkcol-06.txt > > Technical Summary > This specification extends the Web Distributed Authoring and > Versioning (WebDAV) MKCOL method to allow collections of > arbitrary resourcetype to be created and to allow properties > to be set at the same time. It avoids minting new MK* methods > (such as MKCALENDAR) for each new type of collection. > > Working Group Summary > Process was smooth; the only early disagreement was about the > scope of this document (whether it should apply to > non-collection resources as well, and whether it should also > setting ACLs). In the end, the WG converged on the minimal > functionality needed to resolve the issue. > > Document Quality > This protocol extension defined in this document is used > by the VCARDDAV protocol (another deliverable of the Working > Group), for which several vendors have announced support > (for instance, Apple, and Viagenie). > > Personnel > The Document Shepherd for this document was Julian Reschke, > and the responsible Area Director is Alexey Melnikov. From wwwrun@core3.amsl.com Tue Sep 1 16:15:16 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEZIe028416 for ; Tue, 1 Sep 2009 16:14:36 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 012883A6E9A; Tue, 1 Sep 2009 16:14:20 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230525.GH13142@isi.edu> References: <20090831173220.B53D93A6E4E@core3.amsl.com> <20090901230525.GH13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18424 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18424] AutoReply: Re: Protocol Action: 'Elliptic-Curve Algorithm Integration in the Secure Shell Transport Layer' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Elliptic-Curve Algorithm Integration in the Secure Shell Transport Layer' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18424]. Please include the string: [rt.amsl.com #18424] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Aug 31, 2009 at 10:32:20AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Elliptic-Curve Algorithm Integration in the Secure Shell Transport > Layer ' > as a Proposed Standard > > This document has been reviewed in the IETF but is not the product of an > IETF Working Group. > > The IESG contact person is Tim Polk. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-green-secsh-ecc-09.txt > > Technical Summary > > This document describes algorithms based on Elliptic Curve > Cryptography (ECC) for use within the Secure Shell (SSH) transport > protocol. In particular, it specifies: Elliptic Curve Diffie-Hellman > (ECDH) key agreement, Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key > agreement and Elliptic Curve Digital Signature Algorithm (ECDSA) for > use in the SSH Transport Layer protocol. > > Working Group Summary > > This document is the result an individual submission by members of > the community interested in seeing support for use of ECC algorithms > in the SSH protocol. While there is no active working group behind > this work, it was extensively reviewed and discussed on the ietf-ssh > mailing list, which was the home of the Secure Shell Working Group > before that group concluded and still counts many of the participants > of that working group among its members. > > Document Quality > > While there are no existing implementations of this protocol, there > has been indication of interest from SSH implementors. > > Personnel > > The document shepherd for this document is Jeffrey Hutzelman > The responsible Area Director is Tim Polk. > > RFC Editor Note > > Section 12.1 > > Please remove the URL from the reference [FIPS-180-3]. > > Section 12.2 > > Please remove the URLs from references [NIST-800-57] and [NIST-CURVES]. From wwwrun@core3.amsl.com Tue Sep 1 16:15:20 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEZmf028407 for ; Tue, 1 Sep 2009 16:14:36 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 822273A6CE6; Tue, 1 Sep 2009 16:14:20 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230554.GJ13142@isi.edu> References: <20090831173534.E233B28C2AC@core3.amsl.com> <20090901230554.GJ13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18423 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:20 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18423] AutoReply: Re: Document Action: 'Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks' to Informational RFC Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Document Action: 'Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks' to Informational RFC", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18423]. Please include the string: [rt.amsl.com #18423] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Aug 31, 2009 at 10:35:34AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Network Mobility Route Optimization Requirements for Operational Use > in Aeronautics and Space Exploration Mobile Networks ' > as an Informational RFC > > > This document is the product of the Mobility EXTensions for IPv6 Working Group. > > The IESG contact persons are Jari Arkko and Ralph Droms. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mext-aero-reqs-04.txt > > Technical Summary > > This document describes the requirements and desired properties of > Network Mobility (NEMO) Route Optimization techniques for use in > global networked communications systems for aeronautics and space > exploration. > > Working Group Summary > > This is product of the MEXT WG. > > Document Quality > > Substantial input to these requirements was given by aeronautical > communications experts outside the IETF, including members of the > International Civil Aviation Orgnanization (ICAO) and other > aeronautical communications standards bodies. > > Personnel > > The Document Shepherd is Marcelo Braun, and the responsible > Area Director is Jari Arkko. > > RFC Editor Note > > Please change the following: > > OLD: > (e.g. the Gatelink system) > NEW: > (e.g. local networks available while on a gate) > > OLD: > (currently on the surface when connected to a wired Gatelink system) > NEW: > (currently on the surface when connected to a wired link at a gate) > > OLD: > (link technologies and acronyms are briefly defined in Appendix A. > NEW: > (link technologies and acronyms are briefly defined in Appendix A). > > OLD: > rouge > NEW > rogue From wwwrun@core3.amsl.com Tue Sep 1 16:15:23 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEYsh028396 for ; Tue, 1 Sep 2009 16:14:35 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C217E3A6B4C; Tue, 1 Sep 2009 16:14:19 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230609.GK13142@isi.edu> References: <20090901162302.1BEB43A6CB6@core3.amsl.com> <20090901230609.GK13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18421 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:19 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18421] AutoReply: Re: Protocol Action: 'Layered Coding Transport (LCT) Building Block' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Layered Coding Transport (LCT) Building Block' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18421]. Please include the string: [rt.amsl.com #18421] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Tue, Sep 01, 2009 at 09:23:02AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Layered Coding Transport (LCT) Building Block ' > as a Proposed Standard > > > This document is the product of the Reliable Multicast Transport Working Group. > > The IESG contact persons are Magnus Westerlund and Lars Eggert. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-lct-revised-11.txt > > Technical Summary > > This document is an RMT Building Block that specifies protocol headers > and procedures useful for building a reliable multicast transport > protocol that can employ packet-level forward error correction (FEC) > coding to enable massively- scalable, reliable, unidirectional network > data transport without requiring receiver feedback. Layered Coding > Transport is specifically designed to support protocols using IP > multicast, but also provides support to protocols that use unicast. > Layered Coding Transport is compatible with congestion control that > provides multiple rate delivery to receivers. > > Working Group Summary > > There is consensus in the WG to publish this documents. > > Document Quality > > The document is of high quality and has been subject to extensive > review in its Internet Draft and Experimental RFC forms. The > revised draft represents a small number of changes from the original > Experimental RFC 3451. > > Open source implementations of the LCT protocol are available and > considerable experience in using this protocol has been accumulated. > The protocol has been adopted by the Digital Video Broadcasting (DVB) > industry consortium for content delivery. > > The content of this document was already reviewed and approved for > publication as experimental RFC 3451. This document contains minor > technical modifications. > > Personnel > > Brian Adamson is the Document Shepherd. > Magnus Westerlund is the Responsible Area Director. From wwwrun@core3.amsl.com Tue Sep 1 16:15:26 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81NEa2E028418 for ; Tue, 1 Sep 2009 16:14:36 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 6626C3A6CB2; Tue, 1 Sep 2009 16:14:20 -0700 (PDT) From: "IETF-IESG via RT" Reply-To: iesg-secretary@ietf.org In-Reply-To: <20090901230512.GG13142@isi.edu> References: <20090831172431.725CB28C417@core3.amsl.com> <20090901230512.GG13142@isi.edu> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18425 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: rfc-editor@rfc-editor.org To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Tue, 01 Sep 2009 16:14:21 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18425] AutoReply: Re: Protocol Action: 'Alarms in SYSLOG' to Proposed Standard Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Re: Protocol Action: 'Alarms in SYSLOG' to Proposed Standard", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.amsl.com #18425]. Please include the string: [rt.amsl.com #18425] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary@ietf.org ------------------------------------------------------------------------- Greetings, We have added this document to our online queue at: http://www.rfc-editor.org/queue.html Please let us know if you have any questions. Thank you. RFC Editor On Mon, Aug 31, 2009 at 10:24:31AM -0700, The IESG wrote: > The IESG has approved the following document: > > - 'Alarms in SYSLOG ' > as a Proposed Standard > > > This document is the product of the Operations and Management Area Working Group. > > The IESG contact persons are Dan Romascanu and Ron Bonica. > > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-alarm-02.txt > > Technical Summary > > This document describes how to send alarm information in syslog. It > includes the mapping of ITU perceived severities onto syslog message > fields and a number of alarm-specific SD-PARAM definitions from X.733 > and the IETF Alarm MIB. > > Working Group Summary > > The document was revised based on WG feedback & the result meets > the issues that were raised. > > Document Quality > > SYSLOG is widely implemented and deployed, and the ITU severities are > > used by a number of protocols and alarm models including the IETF > Alarm MIB. > > Personnel > > Scott Bradner is the Document Shepherd for this document. Dan > Romascanu is the Responsible Area Director. > > RFC Editor Note > > Please insert the following edits in the published version: > > 1. In section 1, > > Old:Alarm related terminology is defined in [RFC3877]. > > > New:Alarm related terminology is defined in [RFC3877]. > > SD-ID, SD-PARM and other syslog related terms are defined in [RFC5424] > > > 2. In section 3 > > Old: the SD-PARARMS are mandatory. > > New: the SD-PARAMS are mandatory. > > > > 3. In section 3.6 > > Old: [RFC1738] and its updates. In the case of an SNMP resource, the > > New: [RFC3986] and its updates. In the case of an SNMP resource, the > > > > 4. In section 4 > > Old: In this example, extended from [Syslog], the VERSION is 1 and the > New: In this example, extended from [RFC5424], the VERSION is 1 and the > > OLD: 'APP-NAME is "su"' > NEW: 'APP-NAME is "evntslog"' > > OLD: 'exampleSDID@0' > NEW: 'exampleSDID@32473' > > OLD: 'resourceURI =' > NEW: 'resourceURI=' > > 5. In section 6 > > Old: IANA is requested to register the SD-IDs > > New: IANA is requested to register the syslog Structured Data ID Values > > 6. In section 8.1 > > Old: [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, > "Uniform > Resource Locators (URL)", RFC 1738, December 1994. > > New: [RFC3986] Berners-Lee, T., Fielding, R., and Masinter, L., > "Uniform Resource Identifier (URI): Generic Syntax", RFC RFC3986, January > 2005. > > 7. In Section 3.1: > > OLD: If the "alarm" SD-ID is supported, the "resource" SD-PARAM MUST be > supported. > > NEW: If the "alarm" SD-ID is included, the "resource" SD-PARAM MUST be > included. > > 8. In Section 3.2: > > OLD: If the "alarm" SD-ID is supported, the "probableCause" SD-PARAM MUST > > > be supported. > > NEW: If the "alarm" SD-ID is included, the "probableCause" SD-PARAM MUST > be included. > > 9. In Section 3.3: > > OLD: If the "alarm" SD-ID is supported, the "perceivedSeverity" SD-PARAM > MUST be supported. > > NEW: If the "alarm" SD-ID is included, the "perceivedSeverity" SD-PARAM > MUST be included. > > 10. In Section 3.4: > > OLD: If the "alarm" SD-ID is supported, the "eventType" SD-PARAM SHOULD > be supported. > > NEW: If the "alarm" SD-ID is included, the "eventType" SD-PARAM SHOULD be > included. > > 11. In Section 3.5: > > OLD: If the "alarm" SD-ID is supported, the "trendIndication" SD-PARAM > SHOULD be supported. > > NEW: If the "alarm" SD-ID is included, the "trendIndication" SD-PARAM > SHOULD be included. > > 12. In Section 3.6: > > OLD: If the "alarm" SD-ID is supported, the "resourceURI" SD-PARAM SHOULD > > > be supported. > > NEW: If the "alarm" SD-ID is included, the "resourceURI" SD-PARAM SHOULD > be included. From wwwrun@core3.amsl.com Wed Sep 2 07:30:42 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n82ETkVL010834 for ; Wed, 2 Sep 2009 07:29:47 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id D4CCC28C804; Wed, 2 Sep 2009 07:29:19 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18420 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 02 Sep 2009 07:29:19 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18420] Resolved: Re: Protocol Action: 'Multiple Care-of Addresses Registration' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Wed Sep 2 07:31:27 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n82EUe86011168 for ; Wed, 2 Sep 2009 07:30:40 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id BC7143A68C4; Wed, 2 Sep 2009 07:30:23 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18423 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 02 Sep 2009 07:30:23 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18423] Resolved: Re: Document Action: 'Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks' to Informational RFC We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Wed Sep 2 07:32:25 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n82EVVps011460 for ; Wed, 2 Sep 2009 07:31:32 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 8D5DE3A68C4; Wed, 2 Sep 2009 07:31:15 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18427 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 02 Sep 2009 07:31:15 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18427] Resolved: Re: Protocol Action: 'Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Wed Sep 2 07:32:47 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n82EW8wU011633 for ; Wed, 2 Sep 2009 07:32:08 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id C879D3A690E; Wed, 2 Sep 2009 07:31:51 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18424 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 02 Sep 2009 07:31:51 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18424] Resolved: Re: Protocol Action: 'Elliptic-Curve Algorithm Integration in the Secure Shell Transport Layer' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Wed Sep 2 07:33:52 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n82EXBVf012023 for ; Wed, 2 Sep 2009 07:33:12 -0700 (PDT) Received: by core3.amsl.com (Postfix, from userid 30) id 301853A69E9; Wed, 2 Sep 2009 07:32:55 -0700 (PDT) From: "Amy Vezza via RT" Reply-To: iesg-secretary@ietf.org Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #18425 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: avezza@amsl.com To: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 02 Sep 2009 07:32:55 -0700 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: wwwrun@core3.amsl.com Subject: [rt.amsl.com #18425] Resolved: Re: Protocol Action: 'Alarms in SYSLOG' to Proposed Standard We believe that this resolves your issue, and this ticket has therefore been marked as closed in our system. If the issue is not resolved to your satisfaction, or if you have additional questions, please reply to this message using the above trouble ticket number, and your ticket will be automatically reopened. From wwwrun@core3.amsl.com Wed Sep 2 07:34:36 2009 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on boreas.isi.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from mail.ietf.or