Protocol Action: 'Rivest-Shamir-Adleman (RSA) key exchange for the Secure Shell (SSH) Transport Layer Protocol' to Proposed Standard
The IESG has approved the following document: - 'Rivest-Shamir-Adleman (RSA) key exchange for the Secure Shell (SSH) Transport Layer Protocol ' draft-harris-ssh-rsa-kex-06.txt 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 Sam Hartman. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-harris-ssh-rsa-kex-06.txt Technical Summary This memo describes a key-exchange method for the Secure Shell (SSH) protocol based on Rivest-Shamir-Adleman (RSA) public-key encryption. It uses much less client CPU time than the Diffie-Hellman algorithm specified as part of the core protocol, and hence is particularly suitable for slow client systems. Working Group Summary This document is not a product of the secsh working group but it has been reviewed by participants of that working group. Protocol Quality This document has been reviewed by Sam Hartman for the IESG. There are at least two implementations of this specification underway. Note to RFC Editor Remove the trademark notice section prior to publication. Unlike the core ssh documents it is not needed in this case. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)' to Proposed Standard
The IESG has approved the following document: - 'Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP) ' draft-ietf-sip-identity-06.txt as a Proposed Standard This document is the product of the Session Initiation Protocol Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-identity-06.txt Technical Summary The existing security mechanisms in the Session Initiation Protocol are inadequate for cryptographically assuring the identity of the end users that originate SIP requests, especially in an interdomain context. This document specifies a mechanism for securely identifying originators of SIP messages. It does so by defining two new SIP header fields, Identity, for conveying a signature used for validating the identity, and Identity-Info, for conveying a reference to the certificate of the signer. It specifies the mechanisms and procedures for using these and how they can be used with the existing SIP privacy capabilities. It is desirable for SIP user agents to be able to send requests to destinations with which they have no previous association - just as in the telephone network today, one can receive a call from someone with whom one has no previous association, and still have a reasonable assurance that their displayed Caller-ID is accurate. A cryptographic approach, like the one described in this document, can probably provide a much stronger and less-spoofable assurance of identity than the telephone network provides today. Working Group Summary This specification required a number of tries and much analysis. There was strong consensus on the solution by the time it reached the version in this draft. Protocol Quality Eric Rescorla provided early architectural review of the work. The careful reading by the GEN-ART reviewer, Lakshminath Dondeti was valuable. Allison Mankin is the Responsible Area Director. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Optimistic Duplicate Address Detection for IPv6' to Proposed Standard
The IESG has approved the following document: - 'Optimistic Duplicate Address Detection for IPv6 ' draft-ietf-ipv6-optimistic-dad-07.txt as a Proposed Standard This document is the product of the IP Version 6 Working Group Working Group. The IESG contact persons are Margaret Wasserman and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipv6-optimistic-dad-07.txt - Technical Summary Optimistic Duplicate Address Detection is an interoperable modification of the existing IPv6 Neighbor Discovery (RFC2461) and Stateless Address Autoconfiguration (RFC2462) process. The intention is to minimize address configuration delays in the successful case, to reduce disruption as far as possible in the failure case and to remain interoperable with unmodified hosts and routers. - Working Group Summary The IPv6 working group has done extensive review of this document and this document reflects the consensus of the group. - Protocol Quality This document has been reviewed by members of the ipv6@ietf.org mailing list and by the working group chairs. This document was reviewed for the IESG by Margaret Wasserman. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'Low Latency Handoffs in Mobile IPv4' to Experimental RFC
The IESG has approved the following document: - 'Low Latency Handoffs in Mobile IPv4 ' draft-ietf-mobileip-lowlatency-handoffs-v4-11.txt as an Experimental RFC This document is the product of the Mobility for IPv4 Working Group. The IESG contact persons are Margaret Wasserman and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-11.txt Technical Summary Mobile IPv4 describes how a Mobile Node can perform IP-layer handoffs between subnets served by different Foreign Agents. In certain cases, the latency involved in these handoffs can be above the threshold required for the support of delay-sensitive or real-time services. The aim of this document is to present two methods to achieve low-latency Mobile IP handoffs. In addition, a combination of these two methods is described. The described techniques allow greater support for real-time services on a Mobile IPv4 network by minimising the period of time when a Mobile Node is unable to send or receive IP packets due to the delay in the Mobile IP Registration process. Working Group Summary This document is a work item of the MIP4 WG. Protocol Quality This document was reviewed for the IESG by Margaret Wasserman. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Mobile IPv4 Dynamic Home Agent Assignment' to Proposed Standard
The IESG has approved the following document: - 'Mobile IPv4 Dynamic Home Agent Assignment ' draft-ietf-mip4-dynamic-assignment-07.txt as a Proposed Standard This document is the product of the Mobility for IPv4 Working Group. The IESG contact persons are Margaret Wasserman and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-dynamic-assignment-07.txt Technical Summary Mobile IPv4 uses the Home Agent (HA) to anchor sessions of a roaming Mobile Node (MN). This draft proposes a messaging mechanism for dynamic home agent assignment and HA redirection. The goal is to provide a mechanism to assign an optimal HA for a Mobile IP session while allowing any suitable method for HA selection. Working Group Summary This document is a work item of the MIP4 WG. There were several changes made to this document based on AD and IETF LC comments from Thomas Narten and others. Protocol Quality This document has been reviewed for the IESG by Margaret Wasserman. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Fibre-Channel Name Server MIB' to Proposed Standard
The IESG has approved the following document: - 'Fibre-Channel Name Server MIB ' draft-ietf-imss-fc-nsm-mib-05.txt as a Proposed Standard This document is the product of the Internet and Management Support for Storage Working Group. The IESG contact persons are Bert Wijnen and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-05.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 describes managed objects for information related to the Name Server function of a Fibre Channel network. The Fibre Channel Name Server provides a means for Fibre Channel ports to register and discover Fibre Channel names and attributes. Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. Protocol Quality The protocol has been reviewed by Keith McCloghrie for the imss WG. Keith is one in the group of authors. Orly Nicklass did independent MIB Doctor review and Bert Wijnen reviewed this document for the IESG. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Fibre Channel Fabric Address Manager MIB' to Proposed Standard
The IESG has approved the following document: - 'Fibre Channel Fabric Address Manager MIB ' draft-ietf-imss-fc-fam-mib-03.txt as a Proposed Standard This document is the product of the Internet and Management Support for Storage Working Group. The IESG contact persons are Bert Wijnen and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fam-mib-03.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 describes managed objects for information related to a Fibre Channel network's Fabric Address Manager. Fabric Address Manager refers to the functionality of acquiring DomainID(s) as specified in [FC-SW-3], and managing Fibre Channel Identifiers as specified in [FC-FS]. Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. Protocol Quality The protocol has been reviewed for the imss WG by Keith McCloghrie (who is one in the group of authors). Orly Nicklass did independent MIB doctor review and Bert Wijnen reviewed the document for the IESG. Note to RFC Editor - Section 7 is redundant with the back matter. So it is best deleted. - Fix typo (missing e), sect 12 page 40 OLD: t11FamRcFabricNotifyEnabl -- ability to enable/disable a notification. NEW: t11FamRcFabricNotifyEnable -- ability to enable/disable a notification. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'The AES-CMAC Algorithm' to Informational RFC
The IESG has approved the following document: - 'The AES-CMAC Algorithm ' draft-songlee-aes-cmac-03.txt 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 Russ Housley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-songlee-aes-cmac-03.txt Technical Summary AES-CMAC uses the AES cipher block to provide a 128-bit message authentication code (MAC). The document provides clear guidelines on the use of AES-CMAC, test vectors, and test code. Working Group Summary This is an individual submission. Protocol Quality The AES-CMAC is one of choices for the message authentication code (MAC) and key derivation function (KDF) supported in IEEE 802.16e. We believe that AES-CMAC has been immplemented by INTEL, Runcom and SAMSUNG for their IEEE 802.16e-compliant products. We believe that other vendors develop or have developed AES-CMAC for their IEEE 802.16e-compliant products. This document was reviewed by Russ Housley for the IESG. Note to RFC Editor Please delete the reference to [RFC1750] in the informative references. This document is not referenced in the text: [RFC1750] Eastlake 3rd, D., Crocker, S., and J. Schiller, Randomness Recommendations for Security, RFC 1750, December 1994. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
Last Call: 'L2VPN Extensions for L2TP' to Proposed Standard
The IESG has received a request from the Layer Two Tunneling Protocol Extensions WG to consider the following document: - 'L2VPN Extensions for L2TP ' draft-ietf-l2tpext-l2vpn-06.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-01-23. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2vpn-06.txt ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 4285 on Authentication Protocol for Mobile IPv6
A new Request for Comments is now available in online RFC libraries. RFC 4285 Title: Authentication Protocol for Mobile IPv6 Author(s): A. Patel, K. Leung, M. Khalil, H. Akhtar, K. Chowdhury Status: Informational Date: January 2006 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 19 Characters: 40874 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-mip6-auth-protocol-07.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc4285.txt IPsec is specified as the means of securing signaling messages between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6). MIPv6 signaling messages that are secured include the Binding Updates and Acknowledgement messages used for managing the bindings between a Mobile Node and its Home Agent. This document proposes an alternate method for securing MIPv6 signaling messages between Mobile Nodes and Home Agents. The alternate method defined here consists of a MIPv6-specific mobility message authentication option that can be added to MIPv6 signaling messages. This document is a product of the Mobility for IPv6 Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc4285.txt ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 4233 on Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer
A new Request for Comments is now available in online RFC libraries. RFC 4233 Title: Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer Author(s): K. Morneault, S. Rengasami, M. Kalla, G. Sidebottom Status: Standards Track Date: January 2006 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 73 Characters: 157857 Obsoletes: 3057 I-D Tag:draft-ietf-sigtran-rfc3057bis-02.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc4233.txt This document defines a protocol for backhauling of Integrated Services Digital Network (ISDN) Q.921 User messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signaling Gateway (SG) and Media Gateway Controller (MGC). It is assumed that the SG receives ISDN signaling over a standard ISDN interface. This document obsoletes RFC 3057. This document is a product of the Signaling Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc4233.txt ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
