RFC 5924 on Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates

2010-06-23 Thread rfc-editor

A new Request for Comments is now available in online RFC libraries.


RFC 5924

Title:  Extended Key Usage (EKU) for 
Session Initiation Protocol (SIP) X.509 Certificates 
Author: S. Lawrence, V. Gurbani
Status: Experimental
Stream: IETF
Date:   June 2010
Mailbox:scott-i...@skrb.org, 
v...@bell-labs.com
Pages:  8
Characters: 16868
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-sip-eku-08.txt

URL:http://www.rfc-editor.org/rfc/rfc5924.txt

This memo documents an extended key usage (EKU) X.509 certificate
extension for restricting the applicability of a certificate to use
with a Session Initiation Protocol (SIP) service.  As such, in
addition to providing rules for SIP implementations, this memo also
provides guidance to issuers of certificates for use with SIP. 
This document defines an Experimental Protocol for the Internet
community.

This document is a product of the Session Initiation Protocol Working Group of 
the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


RFC 5923 on Connection Reuse in the Session Initiation Protocol (SIP)

2010-06-23 Thread rfc-editor

A new Request for Comments is now available in online RFC libraries.


RFC 5923

Title:  Connection Reuse in the Session 
Initiation Protocol (SIP) 
Author: V. Gurbani, Ed.,
R. Mahy, B. Tate
Status: Standards Track
Stream: IETF
Date:   June 2010
Mailbox:v...@alcatel-lucent.com, 
ro...@ekabal.com, 
br...@broadsoft.com
Pages:  19
Characters: 41905
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-sip-connect-reuse-14.txt

URL:http://www.rfc-editor.org/rfc/rfc5923.txt

This document enables a pair of communicating proxies to reuse a
congestion-controlled connection between themselves for sending
requests in the forwards and backwards direction.  Because the
connection is essentially aliased for requests going in the backwards
direction, reuse is predicated upon both the communicating endpoints
authenticating themselves using X.509 certificates through Transport
Layer Security (TLS).  For this reason, we only consider connection
reuse for TLS over TCP and TLS over Stream Control Transmission
Protocol (SCTP).  This document also provides guidelines on
connection reuse and virtual SIP servers and the interaction of
connection reuse and DNS SRV lookups in SIP.  [STANDARDS TRACK]

This document is a product of the Reliable Multicast Transport 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


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


RFC 5922 on Domain Certificates in the Session Initiation Protocol (SIP)

2010-06-23 Thread rfc-editor

A new Request for Comments is now available in online RFC libraries.


RFC 5922

Title:  Domain Certificates in the Session 
Initiation Protocol (SIP) 
Author: V. Gurbani, S. Lawrence,
A. Jeffrey
Status: Standards Track
Stream: IETF
Date:   June 2010
Mailbox:v...@alcatel-lucent.com, 
scott-i...@skrb.org, 
ajeff...@alcatel-lucent.com
Pages:  17
Characters: 37667
Updates:RFC3261

I-D Tag:draft-ietf-sip-domain-certs-07.txt

URL:http://www.rfc-editor.org/rfc/rfc5922.txt

This document describes how to construct and interpret certain
information in a PKIX-compliant (Public Key Infrastructure using
X.509) certificate for use in a Session Initiation Protocol (SIP)
over Transport Layer Security (TLS) connection.  More specifically,
this document describes how to encode and extract the identity of a
SIP domain in a certificate and how to use that identity for SIP
domain authentication.  As such, this document is relevant both to
implementors of SIP and to issuers of certificates.  [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


___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce