Re: [dns-dir] FW: PRELIMINARY Agenda and Package for September 10, 2009 Telechat

[Olafur Gudmundsson <[e-mail]>]

None of the documents is in the DNS-early warning system.

         Olafur


At 04:04 04/09/2009, Romascanu, Dan (Dan) wrote:
>Please find below the preliminary agenda for the 9/10 IESG telechat.
>Please send me your comments, questions and concerns about the documents
>in review and the proposed WG charters before 9/9 COB.
>
>Thanks and Regards,
>
>Dan
>
>
>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On Behalf Of
>IESG Secretary
>
>
>2.1 WG Submissions
>2.1.1 New Item
>   o draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-10.txt
>     Transmission of IP over Ethernet over IEEE 802.16 Networks (Proposed
>
>     Standard) - 1 of 9
>     Note: Gabriel Montenegro <[e-mail]> is the Document
>
>     Shepherd for this document.
>     Token: Ralph Droms
>   o draft-ietf-mpls-3209-patherr-05.txt
>     Node behavior upon originating and receiving Resource ReserVation
>Protocol
>     (RSVP) Path Error message (BCP) - 2 of 9
>     Note: This document should be processed in a batch with
>     draft-ietf-mpls-gmpls-lsp-reroute and
>draft-ietf-mpls-soft-preemption..
>     draft-ietf-mpls-soft-preemption should be read as the last of the
>batch.
>     Token: Adrian Farrel
>   o draft-ietf-mpls-soft-preemption-18.txt
>     MPLS Traffic Engineering Soft Preemption (Proposed Standard) - 3 of
>9
>
>     Note: This document should be processed in a batch with
>     draft-ietf-mpls-gmpls-lsp-reroute and draft-ietf-mpls-3209-patherr..
>
>     draft-ietf-mpls-soft-preemption should be read as the last of the
>batch.
>     Token: Adrian Farrel
>   o draft-ietf-mpls-gmpls-lsp-reroute-04.txt
>     PathErr Message Triggered MPLS and GMPLS LSP Reroute (Proposed
>Standard) -
>     4 of 9
>     Note: This document should be processed in a batch with
>     draft-ietf-mpls-soft-preemption and draft-ietf-mpls-3209-patherr..
>     draft-ietf-mpls-soft-preemption should be read as the last of the
>batch.
>     Token: Adrian Farrel
>   o draft-ietf-dime-pmip6-03.txt
>     Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility
>Anchor
>     Interaction with Diameter Server (Proposed Standard) - 5 of 9
>     Token: Dan Romascanu
>   o draft-ietf-dime-nai-routing-03.txt
>     Diameter User-Name and Realm Based Request Routing Clarifications
>(Proposed
>     Standard) - 6 of 9
>     Token: Dan Romascanu
>   o draft-ietf-mip4-generic-notification-message-09.txt
>     Generic Notification Message for Mobile IPv4 (Proposed Standard) - 7
>of 9
>     Note: Pete McCann ([e-mail]) is the document
>shepherd.
>
>     Token: Jari Arkko
>   o draft-ietf-pcn-baseline-encoding-05.txt
>     Baseline Encoding and Transport of Pre-Congestion Information
>(Proposed
>     Standard) - 8 of 9
>     Note: Steven Blake ([e-mail]) is the document shepherd.
>
>     Token: Lars Eggert
>   o draft-ietf-pwe3-segmented-pw-13.txt
>     Segmented Pseudowire (Proposed Standard) - 9 of 9
>     Note: Stewart Bryant ([e-mail]) is the document shepherd.
>     Token: Ralph Droms
>
>2.1.2 Returning Item
>NONE
>
>2.2 Individual Submissions
>2.2.1 New Item
>   o draft-rosenberg-sip-app-media-tag-03.txt
>     A Session Initiation Protocol (SIP) Media Feature Tag for MIME
>Application
>     Sub-Types (Proposed Standard) - 1 of 1
>     Token: Robert Sparks
>
>2.2.2 Returning Item
>   o draft-housley-iesg-rfc3932bis-08.txt
>     IESG Procedures for Handling of Independent and IRTF Stream
>Submissions
>     (BCP) - 1 of 1
>     Note: There is no document shepherd
>     Token: Jari Arkko
>
>
>3. Document Actions
>
>3.1 WG Submissions
>         Reviews should focus on these questions: "Is this document a
>reasonable
>         contribution to the area of Internet engineering which it
>covers? If
>         not, what changes would make it so?"
>
>3.1.1 New Item
>   o draft-ietf-sipping-service-identification-03.txt
>     Identification of Communications Services in the Session Initiation
>     Protocol (SIP) (Informational) - 1 of 3
>     Token: Robert Sparks
>   o draft-ietf-hip-nat-traversal-08.txt
>     Basic HIP Extensions for Traversal of Network Address Translators
>     (Experimental) - 2 of 3
>     Note: Gonzalo Camarillo ([e-mail]) is the
>document
>     shepherd.
>     Token: Ralph Droms
>   o draft-ietf-eai-imap-utf8-07.txt
>     IMAP Support for UTF-8 (Experimental) - 3 of 3
>     Note: Harald Alvestrand <[e-mail]> has agreed to
>shepherd
>     the document.. Please note that SecDir and GenArt review comments
>are
>
>     addressed via RFC Editor notes.. Also note that the reference to
>obsolete
>     RFC 1341 is intentional. The name parameter was defined in RFC 1341
>across
>     all media types. The subsequent version of MIME (2045/2046)
>deprecated
>it.
>     Token: Alexey Melnikov
>
>3.1.2 Returning Item
>NONE
>
>3.2 Individual Submissions Via AD
>         Reviews should focus on these questions: "Is this document a
>reasonable
>         contribution to the area of Internet engineering which it
>covers? If
>         not, what changes would make it so?"
>
>3.2.1 New Item
>   o draft-drage-sipping-service-identification-03.txt
>     A Session Initiation Protocol (SIP) Extension for the Identification
>of
>     Services (Informational) - 1 of 1
>     Token: Robert Sparks
>
>3.2.2 Returning Item
>NONE
>3.3 Independent Submissions Via RFC Editor
>         The IESG will use RFC 3932 responses: 1) The IESG has not
>         found any conflict between this document and IETF work; 2) The
>         IESG thinks that this work is related to IETF work done in WG
>         <X>, but this does not prevent publishing; 3) The IESG thinks
>         that publication is harmful to work in WG <X> and recommends
>         not publishing at this time; 4) The IESG thinks that this
>         document violates the IETF procedures for <X> and should
>         therefore not be published without IETF review and IESG
>         approval; 5) The IESG thinks that this document extends an
>         IETF protocol in a way that requires IETF review and should
>         therefore not be published without IETF review and IESG
>approval.
>
>         The document shepherd must propose one of these responses in
>         the Data Tracker note and supply complete text in the IESG
>         Note portion of the write-up. The Area Director ballot positions
>         indicate consensus with the response proposed by the
>         document shepherd.
>
>         Other matters may be recorded in comments, and the comments will
>         be passed on to the RFC Editor as community review of the
>document.
>
>
>3.3.1 New Item
>NONE
>3.3.2 Returning Item
>   o draft-ford-behave-top-07.txt
>     Unintended Consequence of two NAT deployments with Overlapping
>Address
>
>     Space (Informational) - 1 of 1
>     Token: Magnus Westerlund
>
>
>4. Working Group Actions
>4.1 WG Creation
>4.1.1 Proposed for IETF Review
>   o  Virtual World Region Agent Protocol (vwrap) - 1 of 1
>     Token: Alexey Melnikov
>4.1.2 Proposed for Approval
>   o SIP Common Log Format (sipclf) - 1 of 1
>     Token: Robert Sparks
>4.2 WG Rechartering
>4.2.1 Under evaluation for IETF Review
>   o IP Flow Information Export (ipfix) - 1 of 3
>     Token: Dan Romascanu
>   o Security Issues in Network Event Logging (syslog) - 2 of 3
>     Token: Pasi Eronen
>   o Network Endpoint Assessment (nea) - 3 of 3
>     Token: Tim Polk
>4.2.2 Proposed for Approval
>   o DNS Extensions (dnsext) - 1 of 1
>     Token: Ralph Droms
>
>_______________________________________________
>dns-dir mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dns-dir