[Roll] [roll] #88: Data option and ULP
"roll issue tracker" <trac+roll@trac.tools.ietf.org> Wed, 04 April 2012 13:10 UTC
Return-Path: <trac+roll@trac.tools.ietf.org>
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 6CE8921F8738 for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 06:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.392
X-Spam-Level:
X-Spam-Status: No, score=-102.392 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5V7M5ddX9w6e for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 06:10:37 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id DFAF121F86BD for <roll@ietf.org>; Wed, 4 Apr 2012 06:10:34 -0700 (PDT)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1SFPys-0006fm-8w; Wed, 04 Apr 2012 09:10:34 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: roll issue tracker <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: mukul@UWM.EDU, jpv@cisco.com
X-Trac-Project: roll
Date: Wed, 04 Apr 2012 13:10:34 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/roll/trac/ticket/88
Message-ID: <055.6ee5f9af0660881f34d198ae081e0ce4@trac.tools.ietf.org>
X-Trac-Ticket-ID: 88
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: mukul@UWM.EDU, jpv@cisco.com, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Cc: roll@ietf.org
Subject: [Roll] [roll] #88: Data option and ULP
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: roll@ietf.org
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: Wed, 04 Apr 2012 13:10:37 -0000
#88: Data option and ULP Problem (proposed resolution exists) ------------------------------ An option exists for carrying payload. The use of the option (tunnel, transport?) is not described properly. Proposed resolution ------------------------ Add a next header and a sequence to the data option so upper layers can be determined. Discussion ------------- [Pascal] Can the data option be different from one DIO to the next? [Mukul] The contents of the data option are specified by the origin (for the DIO) or the target (for the DRO). In theory, an origin can send different data options in different DIOs it generates for a particular route discovery (assuming that it does generate multiple DIOs; it is very much possible that the origin generates just one DIO and then sits silent). But, then the origin is taking the risk that some of the data options would never each the target(s). I guess the origin might do this if the data sent earlier is now stale and the origin would like the target(s) to receive newer data. [Pascal2] This should be discussed in the draft. You need to set the expectation for the upper layer(s). Is there a way to differentiate different data sets? Eg instance or sequence nb? My suggestion so far is that the data should have 3 bits of next header and 5 bits of sequence. [Mukul2] This sounds good to me. I will incorporate this in the draft unless I hear a better proposal. [Pascal3] Cool. Please make that another LC issue and the proposed resolution, see if there is anyone adding anything to it. [Mukul3] Actually, I would like the next header to be 4 bits and the sequence number to be 4 bits. 4-bit sequence number will still allow up to 16 different messages to be sent during a P2P-RPL discovery. 4 bit next header will allow 16 different possibilities. We can have so many different ways to compress UDP/TCP headers. I think 3 bit next header may not be sufficient. [Pascal4] Cool. Let's use that as the proposed resolution [Mukul4] OK. Pascal -- -----------------------------------+--------------------- Reporter: jpv@… | Owner: mukul@… Type: defect | Status: new Priority: major | Milestone: Component: p2p-rpl | Version: Severity: Submitted WG Document | Keywords: -----------------------------------+--------------------- Ticket URL: <https://svn.tools.ietf.org/wg/roll/trac/ticket/88> roll <http://tools.ietf.org/wg/roll/>
- [Roll] [roll] #88: Data option and ULP roll issue tracker
- Re: [Roll] [roll] #88: Data option and ULP Mukul Goyal
- [Roll] Closure text for ticket #88 Mukul Goyal
- Re: [Roll] Closure text for ticket #88 Pascal Thubert (pthubert)
- Re: [Roll] [roll] #88: Data option and ULP roll issue tracker
- Re: [Roll] [roll] #88: Data option and ULP roll issue tracker
- Re: [Roll] [roll] #88: Data option and ULP roll issue tracker
- Re: [Roll] [roll] #88: Data option and ULP Mukul Goyal
- Re: [Roll] [roll] #88: Data option and ULP roll issue tracker