[MEXT] Some comments on DSMIPv6-07
"Desire Oulai" <desire.oulai@ericsson.com> Mon, 05 January 2009 21:00 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: monami6-archive@megatron.ietf.org
Delivered-To: ietfarch-monami6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id ECC923A6A99;
Mon, 5 Jan 2009 13:00:49 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 5038F28C104
for <mext@core3.amsl.com>; Mon, 5 Jan 2009 13:00:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.308
X-Spam-Level:
X-Spam-Status: No, score=-6.308 tagged_above=-999 required=5 tests=[AWL=0.290,
BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id JXMZSepnjZtJ for <mext@core3.amsl.com>;
Mon, 5 Jan 2009 13:00:47 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
by core3.amsl.com (Postfix) with ESMTP id 6A3D928C0F3
for <mext@ietf.org>; Mon, 5 Jan 2009 13:00:47 -0800 (PST)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
[138.85.77.51])
by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n05L5BjP003024;
Mon, 5 Jan 2009 15:05:11 -0600
Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by
eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 5 Jan 2009 15:00:30 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 16:00:22 -0500
Message-ID: <D373F8710ACBA6419BF0B7A5177691CC059CCA6B@ecamlmw720.eamcs.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Some comments on DSMIPv6-07
Thread-Index: AclveJ+Tc6sBkxv1SymCNIQsZgOhMw==
From: "Desire Oulai" <desire.oulai@ericsson.com>
To: "Hesham Soliman" <hesham@elevatemobile.com>
X-OriginalArrivalTime: 05 Jan 2009 21:00:30.0125 (UTC)
FILETIME=[A45F7DD0:01C96F78]
Cc: mext@ietf.org
Subject: [MEXT] Some comments on DSMIPv6-07
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0160948499=="
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
Hi Hesham, In the text, it is said in section 5.1: " The following value is assigned to the Type field, other values may be assigned in the future: 1 GRE [RFC2784] " In the text before, it is said that you can use just 0 and 1 for the type field. Does this mean we can just add one more value? Why not set the GRE value to 0 rather than 1? Also, still in section 5.1 : " 0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 7: TLV-header format Type This field indicates the type of the payload following this header. Length This field indicates the length of the payload following the header, excluding the TLV-header itself. The use of this flag is described in Section 5 " the sentence "The use of this flag is described in Section 5" should be removed as the length field is not a flag. BR Desire
_______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] Some comments on DSMIPv6-07 Desire Oulai