Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-08.txt
Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 30 January 2008 13:49 UTC
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKDJF-0002oY-Tw; Wed, 30 Jan 2008 08:49:01 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1JKDJE-0002fh-CF for mip4-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 08:49:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKDJE-0002bh-0k for mip4@ietf.org; Wed, 30 Jan 2008 08:49:00 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JKDJD-0005vy-AR for mip4@ietf.org; Wed, 30 Jan 2008 08:48:59 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-119.messagelabs.com!1201700937!20652847!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 31234 invoked from network); 30 Jan 2008 13:48:57 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-5.tower-119.messagelabs.com with SMTP; 30 Jan 2008 13:48:57 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m0UDmvIJ029456; Wed, 30 Jan 2008 06:48:57 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr01.mot.com (8.13.5/Vontu) with SMTP id m0UDmuBh029678; Wed, 30 Jan 2008 07:48:57 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id m0UDmt8m029663; Wed, 30 Jan 2008 07:48:55 -0600 (CST)
Message-ID: <47A08046.2080902@gmail.com>
Date: Wed, 30 Jan 2008 14:48:54 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-08.txt
References: <E1JHSFm-00055N-9c@stiedprstage1.ietf.org> <d3886a520801290709v58acc53dh6a4b06955a61bac2@mail.gmail.com>
In-Reply-To: <d3886a520801290709v58acc53dh6a4b06955a61bac2@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080129-0, 29/01/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org
George Tsirtsis wrote: > Alex, > > I see that v08 still shows all Sub-Types and Code fields in the > message extensions as "TBA". While the extension Type field will be > assigned by IANA, should we not assign numbers to the Sub-Types and > Codes as part of the draft, before it becomes an RFC? or is this > handled differently? Well we took a direction by which we request IANA to assign both that RegReq Type ("Mobile Network Extension") as well as the Sub-Types and the Codes in both MNExtensions and in the existing RegReq and RegRep. This involves modification of existing MIP4 sub-registries and assignments of new ones. The policies of future assignments within the new sub-registries are "Standards Action" or "IESG Approval". This means what it means for "NEMOv4 Tunneling Extension" Sub-Type of draft-ietf-mip4-nemov4-fa-01.txt I think this course of action is satisfying many involved parties. Alex PS: "Standards Action", "IESG Approval" and other policies for future assignments within a new space/registry are desribed in draft-narten-iana-considerations-rfc2434bis-08.txt > > Thanks > George > > 2008/1/22 <Internet-Drafts@ietf.org>: >> A New Internet-Draft is available from the on-line Internet-Drafts directories. >> This draft is a work item of the Mobility for IPv4 Working Group of the IETF. >> >> >> Title : Network Mobility (NEMO) Extensions for Mobile IPv4 >> Author(s) : K. Leung, et al. >> Filename : draft-ietf-mip4-nemo-v4-base-08.txt >> Pages : 25 >> Date : 2008-01-22 >> >> This document describes a protocol for supporting Mobile Networks >> between a Mobile Router and a Home Agent by extending the Mobile IPv4 >> protocol. A Mobile Router is responsible for the mobility of one or >> more network segments or subnets moving together. The Mobile Router >> hides its mobility from the nodes on the mobile network. The nodes >> on the Mobile Network may be fixed in relationship to the Mobile >> Router and may not have any mobility function. >> >> Extensions to Mobile IPv4 are introduced to support Mobile Networks. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-08.txt >> >> To remove yourself from the I-D Announcement list, send a message to >> i-d-announce-request@ietf.org with the word unsubscribe in the body of >> the message. >> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce >> to change your subscription settings. >> >> Internet-Drafts are also available by anonymous FTP. Login with the >> username "anonymous" and a password of your e-mail address. After >> logging in, type "cd internet-drafts" and then >> "get draft-ietf-mip4-nemo-v4-base-08.txt". >> >> A list of Internet-Drafts directories can be found in >> http://www.ietf.org/shadow.html >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> >> Internet-Drafts can also be obtained by e-mail. >> >> Send a message to: >> mailserv@ietf.org. >> In the body type: >> "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-08.txt". >> >> NOTE: The mail server at ietf.org can return the document in >> MIME-encoded form by using the "mpack" utility. To use this >> feature, insert the command "ENCODING mime" before the "FILE" >> command. To decode the response(s), you will need "munpack" or >> a MIME-compliant mail reader. Different MIME-compliant mail readers >> exhibit different behavior, especially when dealing with >> "multipart" MIME messages (i.e. documents which have been split >> up into multiple messages), so check your local documentation on >> how to manipulate these messages. >> >> Below is the data which will enable a MIME compliant mail reader >> implementation to automatically retrieve the ASCII version of the >> Internet-Draft. >> >> >> -- >> Mip4 mailing list: Mip4@ietf.org >> Web interface: https://www1.ietf.org/mailman/listinfo/mip4 >> Charter page: http://www.ietf.org/html.charters/mip4-charter.html >> Supplemental site: http://www.mip4.org/ >> >> > > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/
- [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-08… Internet-Drafts
- Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… George Tsirtsis
- Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-bas… Alexandru Petrescu