draft-ietf-speermint-architecture-02.txt   draft-ietf-speermint-architecture-03.txt 
Speermint Working Group R.Penno (Editor) Speermint Working Group R. Penno
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expires: April 2007 October 20, 2006 Intended status: Informational D. Malas
Expires: September 2007 Level 3
S. Khan
Comcast
A. Uzelac
Global Crossing
April 23, 2007
SPEERMINT Peering Architecture SPEERMINT Peering Architecture
draft-ietf-speermint-architecture-02 draft-ietf-speermint-architecture-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 33 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on November 2006. This Internet-Draft will expire on October 23, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines the SPEERMINT peering architecture, its This document defines the SPEERMINT peering architecture, its
functional components and peering interface functions. functional components and peering interface functions.
Conventions used in this document Conventions used in this document
In examples, "C:" and "S:" indicate lines sent by the client and
server respectively.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [1] document are to be interpreted as described in RFC-2119 Error!
Reference source not found..
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................3
2. Network Context................................................3 2. Network Context................................................3
3. Procedures.....................................................5 3. Procedures.....................................................6
4. Reference SPEERMINT Architecture...............................5 4. Reference SPEERMINT Architecture...............................6
5. Peer Function Examples.........................................6 5. Peer Function Examples.........................................7
5.1. The Location Function (LF) of an Initiating Provider......7 5.1. The Location Function (LF) of an Initiating Provider......8
5.1.1. Target address analysis..............................7 5.1.1. Target address analysis..............................8
5.1.2. User ENUM Lookup.....................................7 5.1.2. User ENUM Lookup.....................................9
5.1.3. Carrier ENUM lookup..................................8 5.1.3. Carrier ENUM lookup..................................9
5.1.4. Routing Table........................................8 5.1.4. Routing Table........................................9
5.1.5. SIP DNS Resolution...................................8 5.1.5. SIP DNS Resolution..................................10
5.1.6. SIP Redirect Server..................................9 5.1.6. SIP Redirect Server.................................10
5.2. The Location Function (LF) of a Receiving Provider........9 5.2. The Location Function (LF) of a Receiving Provider.......10
5.2.1. Publish ENUM records.................................9 5.2.1. Publish ENUM records................................10
5.2.2. Publish SIP DNS records..............................9 5.2.2. Publish SIP DNS records.............................10
5.2.3. TLS..................................................9 5.2.3. TLS.................................................10
5.2.4. IPSec................................................9 5.2.4. IPSec...............................................11
5.2.5. Subscribe Notify....................................10 5.2.5. Subscribe Notify....................................11
5.3. Signaling Function (SF)..................................10 5.3. Signaling Function (SF)..................................11
5.4. Media Function (MF)......................................10 5.4. Media Function (MF)......................................12
5.5. Policy Considerations....................................10 5.5. Policy Considerations....................................12
6. Call Control and Media Control Deployment Options.............11 6. Call Control and Media Control Deployment Options.............13
7. Address space considerations..................................12 7. Address space considerations..................................15
8. Security Considerations.......................................13 8. Security Considerations.......................................15
9. IANA Considerations...........................................13 9. IANA Considerations...........................................15
10. Acknowledgments..............................................13 10. Acknowledgments..............................................15
Author's Addresses...............................................14 11. References...................................................16
11. References...................................................14 11.1. Normative References....................................16
11.1. Normative References....................................14 11.2. Informative References..................................16
11.2. Informative References..................................15 Author's Addresses...............................................18
Intellectual Property Statement..................................16 Intellectual Property Statement..................................18
Disclaimer of Validity...........................................17 Disclaimer of Validity...........................................19
Copyright Statement..............................................17
Acknowledgment...................................................17
1. Introduction 1. Introduction
The objective of this document is to define a reference peering The objective of this document is to define a reference peering
architecture in the context of Session PEERing for Multimedia architecture in the context of Session PEERing for Multimedia
INTerconnect (SPEERMINT). In this process, we define the peering INTerconnect (SPEERMINT). In this process, we define the peering
reference architecture (reference, for short), its functional reference architecture (reference, for short), its functional
components, and peering interface functions from the perspective of a components, and peering interface functions from the perspective of a
real-time communications (Voice and Multimedia) IP Service provider real-time communications (Voice and Multimedia) IP Service provider
network. network.
skipping to change at page 14, line 5 skipping to change at page 16, line 5
10. Acknowledgments 10. Acknowledgments
The working group thanks Sohel Khan for his initial architecture The working group thanks Sohel Khan for his initial architecture
draft that helped to initiate work on this draft. draft that helped to initiate work on this draft.
A significant portion of this draft is taken from [14] with A significant portion of this draft is taken from [14] with
permission from the author R. Mahy. The other important contributor permission from the author R. Mahy. The other important contributor
is Otmar Lendl. is Otmar Lendl.
Author's Addresses
Mike Hammer
Cisco Systems
13615 Dulles Technology Drive
Herndon, VA 20171
USA
Email: mhammer@cisco.com
Sohel Khan, Ph.D.
Technology Strategist
Sprint
6220 Sprint Parkway
Overland Park, KS 66251
U.S.A
Email: Sohel.Q.Khan@sprint.com
Daryl Malas
Level 3 Communications LLC
1025 Eldorado Blvd.
Broomfield, CO 80021
USA
EMail: daryl.malas@level3.com
Reinaldo Penno (Editor)
Juniper Networks
1194 N Mathilda Avenue
Sunnyvale, CA
USA
Email: rpenno@juniper.net
Adam Uzelac
Global Crossing
1120 Pittsford Victor Road
PITTSFORD, NY 14534
USA
Email: adam.uzelac@globalcrossing.com
11. References 11. References
11.1. Normative References 11.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Mealling, M. and R. Daniel, "The Naming Authority Pointer [2] Mealling, M. and R. Daniel, "The Naming Authority Pointer
(NAPTR) DNS Resource Record", RFC 2915, September 2000. (NAPTR) DNS Resource Record", RFC 2915, September 2000.
skipping to change at page 16, line 9 skipping to change at page 17, line 13
terminology-04 (work in progress), May 2006. terminology-04 (work in progress), May 2006.
[13] Mule, J-F., "SPEERMINT Requirements for SIP-based VoIP [13] Mule, J-F., "SPEERMINT Requirements for SIP-based VoIP
Interconnection", draft-ietf-speermint-requirements-00.txt, Interconnection", draft-ietf-speermint-requirements-00.txt,
June 2006. June 2006.
[14] Mahy, R., "A Minimalist Approach to Direct Peering", draft- [14] Mahy, R., "A Minimalist Approach to Direct Peering", draft-
mahy-speermint-direct-peering-00.txt, June 19, 2006. mahy-speermint-direct-peering-00.txt, June 19, 2006.
[15] Penno, R., et al., "SPEERMINT Routing Architecture Message [15] Penno, R., et al., "SPEERMINT Routing Architecture Message
Flows", draft-ietf-speermint-flows-00.txt", August 2006. Flows", draft-ietf-speermint-flows-02.txt", April 2007.
[16] Lee, Y., "Session Peering Use Case for Cable", draft-lee- [16] Lee, Y., "Session Peering Use Case for Cable", draft-lee-
speermint-use-case-cable-00.txt, June, 2006. speermint-use-case-cable-00.txt, June, 2006.
[17] Houri, A., et al., "RTC Provisioning Requirements", draft- [17] Houri, A., et al., "RTC Provisioning Requirements", draft-
houri-speermint-rtc-provisioning-reqs-00.txt, June, 2006. houri-speermint-rtc-provisioning-reqs-00.txt, June, 2006.
[18] Habler, M., et al., "A Federation based VOIP Peering [18] Habler, M., et al., "A Federation based VOIP Peering
Architecture", draft-lendl-speermint-federations-03.txt, Architecture", draft-lendl-speermint-federations-03.txt,
September 2006. September 2006.
skipping to change at page 16, line 42 skipping to change at page 18, line 5
[22] Penno, R., Malas D., and Melampy, P., "A Session Initiation [22] Penno, R., Malas D., and Melampy, P., "A Session Initiation
Protocol (SIP) Event package for Peering", draft-penno-sipping- Protocol (SIP) Event package for Peering", draft-penno-sipping-
peering-package-00 (work in progress), September 2006. peering-package-00 (work in progress), September 2006.
[23] Hollander, D., Bray, T., and A. Layman, "Namespaces in XML", [23] Hollander, D., Bray, T., and A. Layman, "Namespaces in XML",
W3C REC REC-xml-names-19990114, January 1999. W3C REC REC-xml-names-19990114, January 1999.
[24] Burger, E (Ed.), "A Mechanism for Content Indirection in [24] Burger, E (Ed.), "A Mechanism for Content Indirection in
Author's Addresses
Mike Hammer
Cisco Systems
13615 Dulles Technology Drive
Herndon, VA 20171
USA
Email: mhammer@cisco.com
Sohel Khan, Ph.D.
Comcast Cable Communications
U.S.A
Email: sohel_khan@cable.comcast.com
Daryl Malas
Level 3 Communications LLC
1025 Eldorado Blvd.
Broomfield, CO 80021
USA
EMail: daryl.malas@level3.com
Reinaldo Penno (Editor)
Juniper Networks
1194 N Mathilda Avenue
Sunnyvale, CA
USA
Email: rpenno@juniper.net
Adam Uzelac
Global Crossing
1120 Pittsford Victor Road
PITTSFORD, NY 14534
USA
Email: adam.uzelac@globalcrossing.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 17, line 24 skipping to change at page 19, line 22
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 13 change blocks. 
82 lines changed or deleted 91 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/