idnits 2.17.1 draft-mkhalil-mobileip-gnaie-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == The page length should not exceed 58 lines per page, but there was 6 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 7 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 40: '...AI) extension, which SHOULD be used by...' RFC 2119 keyword, line 61: '... SHOULD be used by any Mobile IP ext...' RFC 2119 keyword, line 207: '... 2002 [3]. These MUST NOT conflict with any numbers used in RFC...' RFC 2119 keyword, line 212: '...ed in section 6, MUST NOT conflict wit...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '4' is defined on line 229, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 245, but no explicit reference was found in the text == Outdated reference: A later version (-06) exists of draft-ietf-mobileip-mn-nai-05 ** Obsolete normative reference: RFC 2486 (ref. '2') (Obsoleted by RFC 4282) ** Obsolete normative reference: RFC 2002 (ref. '3') (Obsoleted by RFC 3220) ** Obsolete normative reference: RFC 1700 (ref. '4') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2344 (ref. '5') (Obsoleted by RFC 3024) ** Downref: Normative reference to an Informational RFC: RFC 2356 (ref. '6') == Outdated reference: A later version (-13) exists of draft-ietf-mobileip-challenge-06 == Outdated reference: A later version (-06) exists of draft-ietf-mobileip-3gwireless-ext-00 ** Downref: Normative reference to an Experimental draft: draft-ietf-mobileip-3gwireless-ext (ref. '8') == Outdated reference: A later version (-11) exists of draft-ietf-mobileip-vendor-ext-06 == Outdated reference: A later version (-07) exists of draft-ietf-mobileip-mier-00 -- Possible downref: Normative reference to a draft: ref. '10' Summary: 11 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Mohamed M.Khalil 3 Category: Standards Track Emad Qaddoura 4 Title: draft-mkhalil-mobileip-gnaie-00.txt Haseeb Akhtar 5 Date: February 2000 Nortel Networks 6 Expires: July 2000 Pat R. Calhoun 7 Sun Microsystems, Inc. 9 Generalized NAI Extension (GNAIE) 11 Status of this Memo 13 This document is a submission by the mobile-ip Working Group of the 14 Internet Engineering Task Force (IETF). Comments should be submitted 15 to the MOBILE-IP@STANDARDS.NORTELNETWORKS.COM mailing list. 17 Distribution of this memo is unlimited. 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC2026. Internet-Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its areas, 22 and its working groups. Note that other groups may also distribute 23 working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at: 31 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at: 33 http://www.ietf.org/shadow.html. 35 Abstract 37 The Mobile IP Extensions Rationalization (MIER) specification defines 38 a new extension header format, that is intended to extend the Mobile 39 IP extension address space. This document defines the Generalized 40 Network Access Identifier (NAI) extension, which SHOULD be used by 41 any Mobile IP extension specifying an extension containing an NAI. 43 Table of Contents 45 1.0 Introduction 46 2.0 Generalized NAI Extension 47 2.1 Mobile Node NAI Extension 48 2.2 Foreign Agent NAI Extension 49 2.3 Home Agent NAI Extension 50 2.4 Previous Foreign Agent NAI Extension 51 3.0 IANA Considerations 52 4.0 References 53 5.0 Authors' Address 55 1.0 Introduction 57 The Mobile IP Extensions Rationalization (MIER) specification [10] 58 defines a new extension header format, that is intended to extend the 59 Mobile IP extension address space. This document defines the 60 Generalized Network Access Identifier (NAI) [2] extension, which 61 SHOULD be used by any Mobile IP extension specifying an extension 62 containing an NAI. 64 2.0 Generalized NAI Extension 66 This section defines the generalized NAI Extension, used by any 67 extension that must carry data in the format of an NAI [2]. 69 0 1 2 3 70 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 71 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 72 | Type | Length | Sub-Type | NAI ... 73 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 75 Type 77 TBD (skippable) [3] 79 Length 81 The length of the NAI field 83 Sub-Type 85 This field describes the type of the entity which owns the NAI. 87 NAI 88 Contains the NAI [2] in a string format. 90 2.1 Mobile Node NAI Extension 92 The Mobile Node NAI Extension is subtype 1 of the Generalized NAI 93 extension (see section 2.0) and contains the Mobile Node's NAI. This 94 extension can be found in a Registration Request or Reply [3]. 96 0 1 2 3 97 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | Type | Length | Sub-Type | MN-NAI ... 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 Type 104 TBD (skippable) [3] 106 Length 108 The length of the NAI field 110 Sub-Type 112 1 114 MN-NAI 116 Contains the NAI [2] of the Mobile Node. 118 2.2 Foreign Agent NAI Extension 120 The Foreign Agent NAI Extension is subtype 2 of the Generalized NAI 121 extension (see section 2.0) and contains the Foreign Agent's NAI. 122 This extension can be found in a Registration Request or Reply [3]. 124 0 1 2 3 125 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | Type | Length | Sub-Type | FA-NAI ... 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 Type 132 TBD (skippable) [3] 134 Length 136 The length of the NAI field 138 Sub-Type 140 2 142 FA-NAI 144 Contains the Foreign Agent's NAI [2]. 146 2.3 Home Agent NAI Extension 148 The Home Agent NAI Extension is subtype 3 of the Generalized NAI 149 extension (see section 2.0) and contains the Home Agent's NAI. This 150 extension can be found in a Registration Request or Reply [3]. 152 0 1 2 3 153 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Type | Length | Sub-Type | HA-NAI ... 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 Type 160 TBD (skippable) [3] 162 Length 164 The length of the NAI field 166 Sub-Type 168 3 170 HA-NAI 172 Contains the Home Agent's NAI [2]. 174 2.4 Previous Foreign Agent NAI Extension 176 The Previous Foreign Agent NAI Extension is subtype 4 of the 177 Generalized NAI extension (see section 2.0) and contains the Previous 178 Foreign Agent's NAI. This extension can be found in a Registration 179 Request or Reply [3]. 181 0 1 2 3 182 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Type | Length | Sub-Type | OFA-NAI ... 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 Type 189 TBD (skippable) [3] 191 Length 193 The length of the NAI field 195 Sub-Type 197 4 199 OFA-NAI 201 Contains the Previous Foreign Agent's NAI [2]. 203 3.0 IANA Considerations 205 The number for the General NAI extension is taken from the numbering 206 space defined for Mobile IP registration extensions defined in RFC 207 2002 [3]. These MUST NOT conflict with any numbers used in RFC 208 2002[3], RFC 2344 [5], RFC 2356 [6], Mobile IP Challenge/Response 209 Extensions Draft [7], Mobile IP Network Access Identifier Extensions 210 Draft[1], or Mobile IP Based Micro Mobility Management Protocol in 211 The Third Generation Wireless Network Draft [8]. The Code values 212 specified for errors, listed in section 6, MUST NOT conflict with any 213 other code values listed in RFC 2002[1], RFC 2344 [5], RFC 2356 [6] 214 Mobile IP Challenge/Response Extensions Draft [7], Mobile IP Network 215 Access Identifier Extensions Draft[1], or Mobile IP Based Micro 216 Mobility Management Protocol in The Third Generation Wireless Network 217 Draft [8]. 219 4.0 References 221 [1] Calhoun, Perkins, Mobile IP Network Access Identifier Extension 222 draft-ietf-mobileip-mn-nai-05.txt 224 [2] Aboda, Beadles, "The Network Access Identifier" RFC 2486, January 225 1999 227 [3] C. Perkins, Editor. IP Mobility Support. RFC 2002, October 1996 229 [4] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC 1700, 230 USC/Information Sciences Institute, October 1994. 232 [5] G. Montenegro. Reverse Tunneling for Mobile IP. RFC 2344, May 233 1998. 235 [6] G. Montenegro and V. Gupta. Sun's SKIP Firewall Traversal for 236 Mobile IP. RFC 2356, June 1998. 238 [7] C. Perkins, P. Calhoun. Mobile IP Challenge/Response Extensions. 239 draft-ietf-mobileip-challenge-06.txt, Octobre 1999. 241 [8] Yingchun Xu and et. al. Mobile IP Based Micro Mobility Management 242 Protocol in The Third Generation Wireless Network. draft-ietf- 243 mobileip-3gwireless-ext-00.txt, October 1999. 245 [9] Gopal Dommety and Kent Leung. Mobile IP Vendor/Organization- 246 Specific Extensions. draft-ietf-mobileip-vendor-ext-06.txt. 247 November 1999 249 [10] Khalil, and et. al. Mobile IP Extensions Rationalization (MIER) 250 draft-ietf-mobileip-mier-00.txt, Dec 1999. 252 5.0 Authors' Address 254 Questions about this memo can be directed to: 256 Mohamed Khalil 257 Wireless Technology Labs 258 Nortel Networks 259 2221 Lakeside Blvd. 260 Richardson, TX 75082-4399 261 USA 263 Phone: 1-972-685-0564 264 E-Mail: mkhalil@nortelnetworks.com 266 Emad Qaddoura 267 Wireless Technology Labs 268 Nortel Networks 269 2221 Lakeside Blvd. 270 Richardson, TX 75082-4399 271 USA 273 Phone: 1-972-684-2705 274 E-Mail: emadq@nortelnetworks.com 276 Haseeb Akhtar 277 Wireless Technology Labs 278 Nortel Networks 279 2221 Lakeside Blvd. 280 Richardson, TX 75082-4399 281 USA 283 Phone: 1-972-684-8850 284 E-Mail: haseeb@nortelnetworks.com 286 Pat R. Calhoun 287 Sun Laboratories, Network and Security 288 Sun Microsystems, Inc. 289 15 Network Circle 290 Menlo Park, California, 94025 291 USA 293 Phone: 1-650-786-7733 294 Fax: 1-650-786-6445 295 E-mail: pcalhoun@eng.sun.com