idnits 2.17.1 draft-liu-dmm-mobility-api-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The abstract seems to contain references ([RFC2119]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 5, 2012) is 4428 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.draft-seite-dmm-dma-00' is defined on line 134, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-seite-dmm-dma-00 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Distributed Mobility Managment Working D. Liu 3 Group H. Deng 4 Internet-Draft China Mobile 5 Intended status: Informational March 5, 2012 6 Expires: September 6, 2012 8 Mobility API Extension for DMM 9 draft-liu-dmm-mobility-api-00 11 Abstract 13 RFC 5014 specifies extension to socket API to allow application to 14 specify the preference among multiple source addresses. 15 draft-liu-dmm-address-selection-00 proposes to extend router 16 advertisment message to carry the prefix type information. The 17 mobile node can learn the prefix type information from the router 18 advertisment message. This document proposes an extension to RFC 19 5014 to enable the application to select the DMM related prefixes. 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 6, 2012. 42 Copyright Notice 44 Copyright (c) 2012 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Extension of RFC 5014 . . . . . . . . . . . . . . . . . . . . . 3 60 2. Usage Example . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 63 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 64 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 66 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 69 1. Extension of RFC 5014 71 RFC 5014 defines socket API extension used for source address 72 selection. Application can use this API to override the default 73 source address selection mechnism for IPv6. Currently, RFC 5014 74 defines the following type of source address selection preference: 76 IPV6_PREFER_SRC_HOME /* Prefer Home address as source */ 78 IPV6_PREFER_SRC_COA /* Prefer Care-of address as source */ 80 IPV6_PREFER_SRC_TMP /* Prefer Temporary address as source */ 82 IPV6_PREFER_SRC_PUBLIC /* Prefer Public address as source */ 84 IPV6_PREFER_SRC_CGA /* Prefer CGA address as source */ 86 IPV6_PREFER_SRC_NONCGA /* Prefer a non-CGA address as source */ 88 This document proposes to extend the above definition to add two new 89 flags: 91 IPV6_PREFER_SRC_LOCAL_HNP: 93 Prefer to use locally allocated home network prefix. 95 IPV6_PREFER_SRC_REMOTE_HNP: 97 Prefer to use the home network prefix that allocated by other access 98 router instead of the one that the MN currently attach. 100 2. Usage Example 102 This section gives usage example for this API extension. 104 In DMM scenario, the application on the mobile node can always select 105 the IPV6_PREFER_SRC_LOCAL_HNP as the most preferred soure address. 106 The mobile node's operating system need to guarantee that for the on- 107 going session, it will not interupt the on-going session even there 108 is a new prefix available. 110 3. IANA Considerations 112 This document makes no request of IANA. 114 Note to RFC Editor: this section may be removed on publication as an 115 RFC. 117 4. Security Considerations 119 TBD 121 5. Acknowledgements 123 TBD 125 6. References 127 6.1. Normative References 129 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 130 Requirement Levels", BCP 14, RFC 2119, March 1997. 132 6.2. Informative References 134 [I-D.draft-seite-dmm-dma-00] 135 "Distributed Mobility Anchoring", February 2012. 137 Authors' Addresses 139 Dapeng Liu 140 China Mobile 141 32 Xuanwumen West Street 142 Beijng, Xicheng District 100053 143 China 145 Phone: +86-13911788933 146 Email: liudapeng@chinamobile.com 147 Hui Deng 148 China Mobile 149 32 Xuanwumen West Street 150 Beijng, Xicheng District 100053 151 China 153 Phone: 154 Fax: 155 Email: denghui@chinamobile.com 156 URI: