Protocol Action: 'Bulk DHCPv4 Lease Query' to Proposed Standard (draft-ietf-dhc-dhcpv4-bulk-leasequery-07.txt)
The IESG has approved the following document: - 'Bulk DHCPv4 Lease Query' (draft-ietf-dhc-dhcpv4-bulk-leasequery-07.txt) as Proposed Standard This document is the product of the Dynamic Host Configuration Working Group. The IESG contact persons are Ralph Droms and Brian Haberman. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv4-bulk-leasequery/ Technical Summary The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Leasequery extension allows a requestor to request information about DHCPv4 bindings. This mechanism is limited to queries for individual bindings. In some situations individual binding queries may not be efficient, or even possible. This document extends the DHCPv4 Leasequery protocol to allow for bulk transfer of DHCPv4 address binding data via TCP. Working Group Summary This document received a thorough review by the WG. Many comments were made, and revisions done, but the process was amicable and seems to have satisfied all participants. Document Quality The authors are aware of three client implementations and one server implementation of the protocol. These implementations are of an earlier version of the document, but the authors believe they have gotten a good sense of the quality of the document from the exercise and do not anticipate that the changes that have been made during review will negatively impact interoperability. Personnel Ted Lemon is the Document Shepherd. Ralph Droms is the Responsible Area Director. RFC Editor Note In the IANA Considerations section: OLD: New values for this name space may only be defined by IETF Consensus, as described in [RFC5226]. Basically, this means that they are defined by RFCs approved by the IESG. NEW: New values for this name space may only be defined by IETF Review, as described in [RFC5226].
New Non-WG Mailing List: ssw-agenda-tool -- Discussion of the IETF Agenda Scheduling Tool Project
A new IETF non-working group email list has been created. List address: ssw-agenda-t...@ietf.org Archive: http://www.ietf.org/mail-archive/web/ssw-agenda-tool/ To subscribe: https://www.ietf.org/mailman/listinfo/ssw-agenda-tool Purpose: Discussion of the IETF Agenda Scheduling Tool Project For additional information, please contact the list administrators.
Protocol Action: 'Domain Name System (DNS) IANA Considerations' to Best Current Practice (draft-ietf-dnsext-rfc6195bis-05.txt)
The IESG has approved the following document: - 'Domain Name System (DNS) IANA Considerations' (draft-ietf-dnsext-rfc6195bis-05.txt) as Best Current Practice This document is the product of the DNS Extensions Working Group. The IESG contact persons are Ralph Droms and Brian Haberman. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-dnsext-rfc6195bis/ Technical Summary This document specifies Internet Assigned Number Authority (IANA) parameter assignment considerations for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. Working Group Summary This document is to a large extent the same as its predecessor, but the working group has made some simplifications in process and these were not controversial. There is strong consensus behind this document. Document Quality There are many DNS implementations. This document is high quality due to reviews by a number of strong reviewers/experts including Alfred Hoenes and Mark Andrews. Personnel The document Shepherd is Olafur Gudmundsson o...@ogud.com Ralph Droms is the Responsible Area Director.
Last Call: (IPv6 Guidance for Internet Content and Application Service Providers) to Informational RFC
The IESG has received a request from the IPv6 Operations WG (v6ops) to consider the following document: - 'IPv6 Guidance for Internet Content and Application Service Providers' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2012-12-20. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document provides guidance and suggestions for Internet Content Providers and Application Service Providers who wish to offer their service to both IPv6 and IPv4 customers. Many of the points will also apply to hosting providers, or to any enterprise network preparing for IPv6 users. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-v6ops-icp-guidance/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-v6ops-icp-guidance/ballot/ No IPR declarations have been submitted directly on this I-D.
RFC 6794 on A Framework for Session Initiation Protocol (SIP) Session Policies
A new Request for Comments is now available in online RFC libraries. RFC 6794 Title: A Framework for Session Initiation Protocol (SIP) Session Policies Author: V. Hilt, G. Camarillo, J. Rosenberg Status: Standards Track Stream: IETF Date: December 2012 Mailbox:volker.h...@bell-labs.com, gonzalo.camari...@ericsson.com, jdro...@jdrosen.net Pages: 36 Characters: 94464 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sip-session-policy-framework-10.txt URL:http://www.rfc-editor.org/rfc/rfc6794.txt Proxy servers play a central role as an intermediary in the Session Initiation Protocol (SIP) as they define and impact policies on call routing, rendezvous, and other call features. This document specifies a framework for SIP session policies that provides a standard mechanism by which a proxy can define or influence policies on sessions, such as the codecs or media types to be used. It defines a model, an overall architecture and new protocol mechanisms for session policies. [STANDARDS-TRACK] This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
RFC 6795 on A Session Initiation Protocol (SIP) Event Package for Session-Specific Policies
A new Request for Comments is now available in online RFC libraries. RFC 6795 Title: A Session Initiation Protocol (SIP) Event Package for Session-Specific Policies Author: V. Hilt, G. Camarillo Status: Standards Track Stream: IETF Date: December 2012 Mailbox:volker.h...@bell-labs.com, gonzalo.camari...@ericsson.com Pages: 18 Characters: 42920 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sipping-policy-package-08.txt URL:http://www.rfc-editor.org/rfc/rfc6795.txt This specification defines a Session Initiation Protocol (SIP) event package for session-specific policies. This event package enables user agents (UAs) to subscribe to session policies for a SIP session and to receive notifications if these policies change. [STANDARDS-TRACK] This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
RFC 6796 on A User Agent Profile Data Set for Media Policy
A new Request for Comments is now available in online RFC libraries. RFC 6796 Title: A User Agent Profile Data Set for Media Policy Author: V. Hilt, G. Camarillo, J. Rosenberg, D. Worley Status: Standards Track Stream: IETF Date: December 2012 Mailbox:volker.h...@bell-labs.com, gonzalo.camari...@ericsson.com, jdro...@jdrosen.net, wor...@ariadne.com Pages: 43 Characters: 88634 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-camarillo-rai-media-policy-dataset-04.txt URL:http://www.rfc-editor.org/rfc/rfc6796.txt This specification defines an XML document format to describe the media properties of Session Initiation Protocol (SIP) sessions. Examples for media properties are the codecs or media types used in the session. This document also defines an XML document format to describe policies that limit the media properties of SIP sessions. [STANDARDS-TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC
Protocol Action: 'Specifying Civic Address Extensions in PIDF-LO' to Proposed Standard (draft-ietf-geopriv-local-civic-10.txt)
The IESG has approved the following document: - 'Specifying Civic Address Extensions in PIDF-LO' (draft-ietf-geopriv-local-civic-10.txt) as Proposed Standard This document is the product of the Geographic Location/Privacy Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-geopriv-local-civic/ Technical Summary: This document provides a number of updates to existing IETF civic addressing standards. A backwardly-compatible mechanism for adding civic address elements to the Geopriv civic address format is described. A formal mechanism for handling unsupported extensions when translating between XML and DHCP civic address forms is defined for entities that need to perform this translation. Intial extensions for some new elements are also defined. The LoST (RFC5222) protocol mechanism that returns civic address element names used for validation of location information is clarified and is normatively updated to require a qualifying namespace identifier on each civic address element returned as part of the validation process. Working Group Summary: There was a great deal of WG energy spent on the question of how to balance extensibility of civic addressing (including extensions for local use only) with the need for backwards compatability with existing implementations. In the end we arrived at a solution that the key interested parties are satisfied with. Document Quality: The National Emergency Number Association (NENA) has a technical standard dependent on this work, and several implementations of it are in progress or exist already. There were not any special reviews of this document, although it received substantial attention throughout the process from many core working group members. Personnel: Alissa Cooper is the document shepherd. Robert Sparks in the responsible area director. RFC Editor Note: Section 3.2 Under figure 3: OLD: Length is the number of octets used to represent the namespace URI, local name and value. NEW: Length is the number of octets used to represent the namespace URI, local name and value. The length includes the space between the namespace URI and local name and the space between the local name and value fields.
