Network Working Group                                       Yuankui.zhao
Internet-Draft                                Shanghai Huawei Technology
Intended status: Standards Track                           July 1, 2007
Expires: Jan 1, 2008



               IP option for Sip to decide the destination
                    draft-zhao-sipping-mip-00

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 1,2008                           [Page 1]


Internet-Draft   IP option for Sip to decide the destination  July,2007


Abstract

   At now the mip is popular more and more.Based on mip technology, sip
didn't need to take care of it any thing?


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 1,2008                           [Page 2]


Internet-Draft   IP option for Sip to decide the destination  July,2007


1.  Introduction

   Currently the mip is applied more and more populiar. That is a
   transport technology ,but if that means sip didn't need to take care
   it any more?
   Based on the selection CoA or HoA,the application will have a indeed
   difference in the route cost,source provide and so on. So we
   introduce something to resolve this problem in this draft.


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 1,2008                           [Page 3]


Internet-Draft   IP option for Sip to decide the destination  July,2007


2.  Overview

   SIP protocol can take care of the IP address generaged or utilized
   by mip or other ip transport technologies.







































Yuankui zhao              Jan 1,2008                           [Page 4]


Internet-Draft   IP option for Sip to decide the destination  July,2007


3.  The IP address Suboption

   TBD.







































Yuankui zhao              Jan 1,2008                           [Page 5]


Internet-Draft   IP option for Sip to decide the destination  July,2007


4.  Application scenarios

   TBD.



























Yuankui zhao              Jan 1,2008                          [Page 6]


Internet-Draft   IP option for Sip to decide the destination  July,2007


5.  Security Considerations

   TBD.












































Yuankui zhao              Jan 1,2008                           [Page 7]


Internet-Draft   IP option for Sip to decide the destination  July,2007


6.  Conclusions

   TBD.

















































Yuankui zhao               Jan 1,2008                           [Page 8]


Internet-Draft   IP option for Sip to decide the destination  July,2007

7.  References

7.1.  Normative References

    [STANDARDS]
              "Key words for use in RFCs to Indicate Requirement
              Levels", RFC 2119, March 1997,
              <ftp://ftp.isi.edu/in-notes/rfc2119>.















































Yuankui zhao               Jan 1,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 1,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 1,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 1,2008                         [Page 12]