Ongoing Call for Comment: 'Privacy Considerations for Internet Protocols'
This is a reminder of an ongoing IETF-wide Call for Comment on 'Privacy Considerations for Internet Protocols'. The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here: http://tools.ietf.org/html/draft-iab-privacy-considerations The Call for Comment will last until February 18, 2013. Please send comments to iab at iab.org or submit them via TRAC (see below). === Submitting Comments via TRAC 1. To submit an issue in TRAC, you first need to login to the IAB site on the tools server: http://tools.ietf.org/wg/iab/trac/login 2. If you don't already have a login ID, you can obtain one by navigating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can file an issue by navigating to the ticket entry form: http://trac.tools.ietf.org/wg/iab/trac/newticket 4. When opening an issue: a. The Type: field should be set to defect for an issue with the current document text, or enhancement for a proposed addition of functionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. For example, editorial issues are typically minor or trivial. c. The Milestone: field should be set to milestone1 (useless, I know). d. The Component: field should be set to the document you are filing the issue on. e. The Version: field should be set to 1.0. f. The Severity: field should be set to based on the status of the document (e.g. In WG Last Call for a document in IAB last call) g. The Keywords: and CC: fields can be left blank unless inspiration seizes you. h. The Assign To: field is generally filled in with the email address of the editor. 5. Typically it won't be necessary to enclose a file with the ticket, but if you need to, select I have files to attach to this ticket. 6. If you want to preview your Issue, click on the Preview button. When you're ready to submit the issue, click on the Create Ticket button. 7. If you want to update an issue, go to the View Tickets page: http://trac.tools.ietf.org/wg/iab/trac/report/1 Click on the ticket # you want to update, and then modify the ticket fields as required.
Ongoing Call for Comment: 'Issues in Identifier Comparison for Security Purposes'
This is a reminder of an ongoing IETF-wide Call for Comment on 'Issues in Identifier Comparison for Security Purposes'. The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here: http://tools.ietf.org/html/draft-iab-identifier-comparison The Call for Comment will last until February 10, 2013. Please send comments to iab at iab.org or submit them via TRAC (see below). === Submitting Comments via TRAC 1. To submit an issue in TRAC, you first need to login to the IAB site on the tools server: http://tools.ietf.org/wg/iab/trac/login 2. If you don't already have a login ID, you can obtain one by navigating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can file an issue by navigating to the ticket entry form: http://trac.tools.ietf.org/wg/iab/trac/newticket 4. When opening an issue: a. The Type: field should be set to defect for an issue with the current document text, or enhancement for a proposed addition of functionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. For example, editorial issues are typically minor or trivial. c. The Milestone: field should be set to milestone1 (useless, I know). d. The Component: field should be set to the document you are filing the issue on. e. The Version: field should be set to 1.0. f. The Severity: field should be set to based on the status of the document (e.g. In WG Last Call for a document in IAB last call) g. The Keywords: and CC: fields can be left blank unless inspiration seizes you. h. The Assign To: field is generally filled in with the email address of the editor. 5. Typically it won't be necessary to enclose a file with the ticket, but if you need to, select I have files to attach to this ticket. 6. If you want to preview your Issue, click on the Preview button. When you're ready to submit the issue, click on the Create Ticket button. 7. If you want to update an issue, go to the View Tickets page: http://trac.tools.ietf.org/wg/iab/trac/report/1 Click on the ticket # you want to update, and then modify the ticket fields as required.
Document Action: 'Use Cases and Interpretation of RPKI Objects for Issuers and Relying Parties' to Informational RFC (draft-ietf-sidr-usecases-06.txt)
The IESG has approved the following document: - 'Use Cases and Interpretation of RPKI Objects for Issuers and Relying Parties' (draft-ietf-sidr-usecases-06.txt) as Informational RFC This document is the product of the Secure Inter-Domain Routing Working Group. The IESG contact persons are Stewart Bryant and Adrian Farrel. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-sidr-usecases/ Technical Summary This document provides use cases, directions, and interpretations for organizations and relying parties when creating or encountering RPKI object scenarios in the public RPKI. All of the above are discussed here in relation to the Internet routing system. Working Group Summary One reviewer suggested to expand the usecases to cover ongoing work that is out of the scope of the current document. The draft as is has utility at the present time. Future documents can address additional usecases if and when needed. Nothing else to report, apart from the document taking a bit longer in the WG than expected. Document Quality Several prototype implementations (and even commercial for some parts) exist. Reviewers attention is drawn to the Section 1.2 which describes why RFC1918 prefixes are used rather than the RFC5737 prefixes. This was discussed in the Working Group and was the agreed way forward. Personnel Alexey Melnikov is the document shepherd. Stewart Bryant is the Responsible AD. RFC Editor Note In the acknowledgements please s/Stephen Farrel/Stephen Farrell/
RFC 6864 on Updated Specification of the IPv4 ID Field
A new Request for Comments is now available in online RFC libraries. RFC 6864 Title: Updated Specification of the IPv4 ID Field Author: J. Touch Status: Standards Track Stream: IETF Date: February 2013 Mailbox:to...@isi.edu Pages: 19 Characters: 44418 Updates:RFC791, RFC1122, RFC2003 I-D Tag:draft-ietf-intarea-ipv4-id-update-07.txt URL:http://www.rfc-editor.org/rfc/rfc6864.txt The IPv4 Identification (ID) field enables fragmentation and reassembly and, as currently specified, is required to be unique within the maximum lifetime for all datagrams with a given source address/destination address/protocol tuple. If enforced, this uniqueness requirement would limit all connections to 6.4 Mbps for typical datagram sizes. Because individual connections commonly exceed this speed, it is clear that existing systems violate the current specification. This document updates the specification of the IPv4 ID field in RFCs 791, 1122, and 2003 to more closely reflect current practice and to more closely match IPv6 so that the field's value is defined only when a datagram is actually fragmented. It also discusses the impact of these changes on how datagrams are used. [STANDARDS-TRACK] This document is a product of the Internet Area Working Group Working Group of the IETF. This is now a Proposed Standard. 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 6869 on vCard KIND:device
A new Request for Comments is now available in online RFC libraries. RFC 6869 Title: vCard KIND:device Author: G. Salgueiro, J. Clarke, P. Saint-Andre Status: Standards Track Stream: IETF Date: February 2013 Mailbox:gsalg...@cisco.com, jcla...@cisco.com, psain...@cisco.com Pages: 9 Characters: 14648 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-salgueiro-vcarddav-kind-device-07.txt URL:http://www.rfc-editor.org/rfc/rfc6869.txt This document defines a value of device for the vCard KIND property so that the vCard format can be used to represent computing devices such as appliances, computers, or network elements (e.g., a server, router, switch, printer, sensor, or phone). [STANDARDS-TRACK] This is now a Proposed Standard. 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
