Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10.txt
Mukul Goyal <mukul@uwm.edu> Mon, 07 May 2012 09:36 UTC
Return-Path: <prvs=467a60657=mukul@uwm.edu>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2058421F844C for <roll@ietfa.amsl.com>; Mon, 7 May 2012 02:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.479
X-Spam-Level:
X-Spam-Status: No, score=-6.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GakKRxWG3kRK for <roll@ietfa.amsl.com>; Mon, 7 May 2012 02:36:00 -0700 (PDT)
Received: from ip2mta.uwm.edu (ip2mta.uwm.edu [129.89.7.20]) by ietfa.amsl.com (Postfix) with ESMTP id B140621F851B for <roll@ietf.org>; Mon, 7 May 2012 02:35:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAGKWp09/AAAB/2dsb2JhbABEhXKwFAEBBSNWDA8RBAEBAwINGQIeMwgGEwkQh3ULp3eERYRFiQmBL4lQJYRjgRgEhxOBUY0agRGLGYQYgwc
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id ECA1B12E3BB; Mon, 7 May 2012 04:35:58 -0500 (CDT)
X-Virus-Scanned: amavisd-new at mta02.pantherlink.uwm.edu
Received: from mta02.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta02.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sp6w-jz-KIBy; Mon, 7 May 2012 04:35:58 -0500 (CDT)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id 486B712E3AD; Mon, 7 May 2012 04:35:58 -0500 (CDT)
Date: Mon, 07 May 2012 04:35:58 -0500
From: Mukul Goyal <mukul@uwm.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <1160202689.290337.1336383358180.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <7457.1336331890@marajade.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [99.20.249.193]
X-Mailer: Zimbra 6.0.15_GA_2995 (ZimbraWebClient - IE8 (Win)/6.0.15_GA_2995)
X-Authenticated-User: mukul@uwm.edu
Cc: roll@ietf.org
Subject: Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 09:36:01 -0000
Hi Michael Does the following text meets your concerns? Thanks Mukul Section 7.2 (Data Option) "o Upper: A 4-bit field that identifies the upper layer protocol header with which the information in the Data field starts. A value 0x0 in this field identifies UDP as the upper layer protocol while the value 0xF is reserved for Private Use as defined in [RFC5226]. The other values are Unassigned [RFC5226] at present. " Section 14. IANA Considerations 14.1. Additions to Mode of Operation This document defines a new Mode of Operation, entitled "P2P Route Discovery Mode" (see Section 6), assigned a value of 4 from the "Mode of Operation" space [to be removed upon publication: http://www.iana.org/assignments/rpl/rpl.xml#mop] [RFC6550]. +-------+---------------------------------------+---------------+ | Value | Description | Reference | +-------+---------------------------------------+---------------+ | 4 | P2P Route Discovery Mode of Operation | This document | +-------+---------------------------------------+---------------+ Mode of Operation 14.2. Additions to RPL Control Message Options This document defines two new RPL options: o "P2P Route Discovery Option" (see Section 7.1), assigned a value of 0x0A from the "RPL Control Message Options" space [to be removed upon publication: http://www.iana.org/assignments/rpl/ rpl.xml#control-message-options] [RFC6550]. o "Data Option" (see Section 7.2), assigned a value of 0x0B from the "RPL Control Message Options" space [to be removed upon publication: http://www.iana.org/assignments/rpl/ rpl.xml#control-message-options] [RFC6550]. +-------+---------------------+---------------+ | Value | Meaning | Reference | +-------+---------------------+---------------+ | 0x0A | P2P Route Discovery | This document | | 0x0B | Data | This document | +-------+---------------------+---------------+ RPL Control Message Options 14.3. Additions to RPL Control Codes This document defines the following new RPL messages: o "Discovery Reply Object" (see Section 8), assigned a value of 0x04 from the "RPL Control Codes" space [to be removed upon publication: http://www.iana.org/assignments/rpl/rpl.xml#control-codes] [RFC6550]. o "Discovery Reply Object Acknowledgement" (see Section 10), assigned a value of 0x05 from the "RPL Control Codes" space [to be removed upon publication: http://www.iana.org/assignments/rpl/rpl.xml#control-codes] [RFC6550]. o "Secure Discovery Reply Object" (see Section 8.1), assigned a value of 0x84 from the "RPL Control Codes" space [to be removed upon publication: http://www.iana.org/assignments/rpl/rpl.xml#control-codes] [RFC6550]. o "Secure Discovery Reply Object Acknowledgement" (see Section 10), assigned a value of 0x85 from the "RPL Control Codes" space [to be removed upon publication: http://www.iana.org/assignments/rpl/rpl.xml#control-codes] [RFC6550]. +------+--------------------------------------------+---------------+ | Code | Description | Reference | +------+--------------------------------------------+---------------+ | 0x04 | Discovery Reply Object | This document | | 0x05 | Discovery Reply Object Acknowledgement | This document | | 0x84 | Secure Discovery Reply Object | This document | | 0x85 | Secure Discovery Reply Object | This document | | | Acknowledgement | | +------+--------------------------------------------+---------------+ RPL Control Codes 14.4. New Registry for Upper Layer Headers inside Data Option The Data Option (see Section 7.2) defines a 4-bit "Upper" field, for which IANA is requested to create and maintain a new registry titled "Upper Layer Header Type Inside RPL Data Option". New codes may be allocated in this registry only by an IETF Review [RFC5226]. Each code is tracked with the following characteristics: o Value o Description o Reference The following codes are currently defined: +---------+-------------+---------------+ | Value | Description | Reference | +---------+-------------+---------------+ | 0x0 | UDP Header | This document | | 0x1-0xE | Unassigned | | | 0xF | Private Use | This document | +---------+-------------+---------------+ Upper Layer Header Types Inside RPL Data Option ----- Original Message ----- From: "Michael Richardson" <mcr+ietf@sandelman.ca> To: "Mukul Goyal" <mukul@uwm.edu> Cc: roll@ietf.org Sent: Sunday, May 6, 2012 2:18:10 PM Subject: Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10.txt >>>>> "Mukul" == Mukul Goyal <mukul@uwm.edu> writes: Mukul> This version takes care of all the tickets created for last Mukul> call comments. Mukul> To see the text specific to a particular ticket "xx", search Mukul> for "\begin issue_xx" in: Mukul> https://pantherfile.uwm.edu/mukul/public/files/draft-ietf-roll-p2p-rpl-10.txt Thank you that was helpful. I reopened ticket #88. http://trac.tools.ietf.org/wg/roll/trac/ticket/88 The resolution in -10 is acceptable, but is not complete. "The other values are reserved at present." is not enough. We need an amending formula as part of the IANA instructions. I suggest Standards Action. http://tools.ietf.org/html/rfc5226 section 4.2 gives details. IANA also asks that you refer to the registry by URL that you want to allocate for the other three code point allocations you have made. You can suggest values as you have, but they are supposed to be suggestions.. Also, you might want reserve 0xf as Private Use. -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE> then sign the petition.
- [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10.txt internet-drafts
- Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10… Mukul Goyal
- Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10… Michael Richardson
- Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10… Mukul Goyal
- Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10… Michael Richardson
- Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10… Mukul Goyal
- Re: [Roll] I-D Action: draft-ietf-roll-p2p-rpl-10… Michael Richardson