Network Working Group Yuankui.zhao Internet-Draft Shanghai Huawei Technology Intended status: Standards Track July 9, 2007 Expires: Jan 10, 2008 IP option for Sip to decide the destination draft-zhao-sipping-mip-01 Status of this Memo By submitting this Internet-Draft, each author represents that 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 becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on September 5, 2007. Copyright Notice Copyright (C) The Internet Trust (2007). Yuankui zhao Jan 10,2008 [Page 1] Internet-Draft IP option for Sip to decide the destination July,2007 Abstract Today,a MN has so many address can be used to be connected in a sip [1]communication. Which one is better for the use in the specific environment?This draft provide a mechnism to do this by introducing a new sdp[2] suboption. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. The IP address Suboption . . . . . . . . . . . . . . . . . . . 5 4. Application scenarios . . . . . . . . . . . . .. . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . . . 12 Yuankui zhao Jan 10,2008 [Page 2] Internet-Draft IP option for Sip to decide the destination July,2007 1. Introduction Today,a MN maybe have many address. Some of them is used in one network,but others are used in another network. Focus on the Mip technology,it provide two addresses to MN at least. One is for visit network,named care-of-address,and another is for home network,named home address. To IPv6 terminal,that care-of-address is just the co-located address. Meanwhile,if we use some other technology,such as the dual anchor technology,then there is maybe another home address or a simple IP address is available to this termial. So much addresses are used in difference network scope.For example, care-of-address is used in visited network and home address is used in home network,and so on. So considering the MN's location,then it is the best if we can use difference address to difference service in difference network scope. This will bring a significant advance in the receiving of service. 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC 2119 [STANDARDS]. Yuankui zhao Jan 10,2008 [Page 3] Internet-Draft IP option for Sip to decide the destination July,2007 2. Overview To the two parties in a sip communication,we can specify the address of each other in sdp to let the other know where the communication should to be established. Faced to so many difference IP address of a MN,we can design a mechanism to let the parties in a sip communication can find and decide which address is more fit the environment of that communication. And then to use it. Generally,this mechanism need the transport of those ip address informations, the decision of which ip address to be used,and others need to be considered. In this draft,we introduce a mechanism to achieve this goal. Yuankui zhao Jan 10,2008 [Page 4] Internet-Draft IP option for Sip to decide the destination July,2007 3. The IP address Suboption To make a decision among those difference IP address of a MN for a specific sip communication,we can define a IP address suboption in sdp to describe these information. In this suboption,there will include the necessary information here. Generally, the combination of ip address,port,location infomation will be included. Yuankui zhao Jan 10,2008 [Page 5] Internet-Draft IP option for Sip to decide the destination July,2007 4. Application scenarios In the following,we discuss some typical application scenario to explain the use of this suboption. 4.1 In mip scenario In the mip scenario,this suboption will just like the following: id: The index of this item in the suboption. ip address:the ip address ,that format can be digital or FQDN. port:The communication can be used in this ip address. address type:the type of this ip address.Such as:HoA or CoA. To the specific format of this suboption and it's TLV can be defined more exactly later. 4.2 In dual anchor scenario In dual anchor scenario,this suboption can very similiar with that above. But to the detail explanation of the difference field in that suboption,we can define the address type to specific the specific network scope. For example, we can use the network domain name to describe it. Yuankui zhao Jan 10,2008 [Page 6] Internet-Draft IP option for Sip to decide the destination July,2007 5. Security Considerations The security considerations to this mechanism follow what we have had to use for sip&sdp protocol at now.Of course,when we need to provide seperatelly a specific security protection,we can do that in the future. Yuankui zhao Jan 10,2008 [Page 7] Internet-Draft IP option for Sip to decide the destination July,2007 6. Conclusions At now MN have some many difference ip addresses are used to be communicated in difference scope.In difference environment,diffenerce ip address can be apply to make the communication more efficency.So we can use this mechanism to interactive between the peers of a sip communication to share their ip addresses information and make a decision to use the best one to communicate each other. Yuankui zhao Jan 10,2008 [Page 8] Internet-Draft IP option for Sip to decide the destination July,2007 7. References 7.1. Normative References [1] J. Rosenberg, H. Schulzrinne, "SIP: Session Initiation Protocol", RFC 3261, June 2002. [2] M. Handley, V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998. [STANDARDS] "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997, . Yuankui zhao Jan 10,2008 [Page 9] Internet-Draft IP option for Sip to decide the destination July,2007 8. IANA Considerations This document has no actions for IANA. Yuankui zhao Jan 10,2008 [Page 10] Internet-Draft IP option for Sip to decide the destination July,2007 Authors' Addresses Yuankui Zhao Shanghai Huawei Technology Co.LTD Qian Chang Building No.450 Jin Yu Road Pudong Shanghai,201206 china Phone: Email: John.zhao@huawei.com Yuankui zhao Jan 10,2008 [Page 11] Internet-Draft IP option for Sip to decide the destination July,2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Yuankui zhao Jan 10,2008 [Page 12]