Re: [manet] [Int-area] SMF and intarea-ipv4-id-update

Joe Touch <touch@isi.edu> Wed, 30 March 2011 12:49 UTC

Return-Path: <touch@isi.edu>
X-Original-To: manet@core3.amsl.com
Delivered-To: manet@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F07053A6A1C; Wed, 30 Mar 2011 05:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.775
X-Spam-Level:
X-Spam-Status: No, score=-103.775 tagged_above=-999 required=5 tests=[AWL=-1.176, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 z3QxTJYqorW2; Wed, 30 Mar 2011 05:49:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id D4F9D3A67FC; Wed, 30 Mar 2011 05:49:35 -0700 (PDT)
Received: from [130.129.21.87] (dhcp-1557.meeting.ietf.org [130.129.21.87]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p2UCof2B021128 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 30 Mar 2011 05:50:56 -0700 (PDT)
Message-ID: <4D932721.9070804@isi.edu>
Date: Wed, 30 Mar 2011 05:50:41 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <DEC49BE6-4A03-4A6C-B50E-35CA8794E4E5@inf-net.nl><4D9317FB.6060109@isi.edu> <AE85A629-2790-4060-AEF7-290FC295B741@inf-net.nl> <4D932043.2040006@earthlink.net> <BB69254A-3D6D-46CD-B7EC-8117E5FC2237@inf-net.nl>
In-Reply-To: <BB69254A-3D6D-46CD-B7EC-8117E5FC2237@inf-net.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Wed, 30 Mar 2011 14:11:45 -0700
Cc: MANET IETF <manet@ietf.org>, int-area@ietf.org
Subject: Re: [manet] [Int-area] SMF and intarea-ipv4-id-update
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 12:49:37 -0000

FWIW, Briscoe's doc won't help here. It is intended to find other ways 
to use the ID field for atomic packets (as defined in ipv4-id-update), 
but those bits would be as flags, not as a whole space that could be 
used for a given purpose.

Joe

On 3/30/2011 5:34 AM, Teco Boot wrote:
> There are other ideas around, that could be applicable in MANETs.
> You could check draft-briscoe-intarea-ipv4-id-reuse
>
> Teco
>
> Op 30 mrt 2011, om 14:21 heeft Charles E. Perkins het volgende geschreven:
>
>>
>> Hello Teco,
>>
>> Is it possible that the SMF usage is not vulnerable to
>> the pitfalls noted in the intarea draft?  Usually we
>> don't picture NAT boxes in the MANET routing paths...
>>
>> Regards,
>> Charlie P.
>>
>>
>> On 3/30/2011 5:01 AM, Teco Boot wrote:
>>> Hi Joe,
>>>
>>> The current text in intarea-ipv4-id-update is "no current deployments
>>> are known". I read this as a statement in general. Then, it is not correct.
>>> I am fine with discouragement of usage of systems that use IP_ID for DPD,
>>> but such systems are around.
>>>
>>> Teco
>>>
>>>
>>> Op 30 mrt 2011, om 13:46 heeft Joe Touch het volgende geschreven:
>>>
>>>> Hi, Teco,
>>>>
>>>> On 3/30/2011 4:29 AM, Teco Boot wrote:
>>>>> Sorry for x-posting. But there is a conflict in:
>>>>> http://tools.ietf.org/html/draft-ietf-manet-smf
>>>>> http://tools.ietf.org/html/draft-ietf-intarea-ipv4-id-update
>>>>>
>>>>> SMF has a duplicate packet detection function based on the IPv4
>>>>> ID field. So text in ietf-intarea-ipv4-id-update section 4
>>>>> is not correct, in that there would be no deployments for such.
>>>>
>>>> SMF is experimental. When we talk about deployments of duplicate detection, we're focused on standards-based systems.
>>>>
>>>> Note that ipv4-id-update is standards-track.
>>>>
>>>>> That said, SMF deployment with IPv4 DPD on IP-ID would be limited.
>>>>>
>>>>> What to do?
>>>>
>>>> IMO, recommend H-DPD and change the discussion to explain why the ID shouldn't be used for DPD (the text is basically already there - it mentions the idea, but then explains that it's not likely to work anyway).
>>>>
>>>> Use of the IP ID for this purpose is problematic for a variety of reasons, which is why ipv4-id-update deprecates use of that field for that purpose.
>>>>
>>>> Joe
>>>
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>
>>
>