Re: draft-kaiser-nd-pd-00.txt (was: Announcing Prefix Delegation extensions to ND)

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 03 November 2012 02:01 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3531F21F9C14 for <ipv6@ietfa.amsl.com>; Fri, 2 Nov 2012 19:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.178
X-Spam-Level:
X-Spam-Status: No, score=-2.178 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kIXHa0zq5-XZ for <ipv6@ietfa.amsl.com>; Fri, 2 Nov 2012 19:01:28 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C39F421F9803 for <ipv6@ietf.org>; Fri, 2 Nov 2012 19:01:28 -0700 (PDT)
Received: from sandelman.ca (ip-64-134-66-63.public.wayport.net [64.134.66.63]) by relay.sandelman.ca (Postfix) with ESMTPS id 7DCD881A9 for <ipv6@ietf.org>; Fri, 2 Nov 2012 21:53:31 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E5575CA0C8 for <ipv6@ietf.org>; Fri, 2 Nov 2012 15:59:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IPv6 <ipv6@ietf.org>
Subject: Re: draft-kaiser-nd-pd-00.txt (was: Announcing Prefix Delegation extensions to ND)
In-reply-to: <5092D325.2010605@gmail.com>
References: <5081087D.2020807@gmail.com> <alpine.DEB.2.00.1210191006140.28593@uplift.swm.pp.se> <CAC8QAccjPmKhk3dJQC8KHRFuDUvNYOY-sdfnN7GAcdwEbVHKwA@mail.gmail.com> <alpine.DEB.2.00.1210191814280.28593@uplift.swm.pp.se> <5082C948.3080109@gmail.com> <alpine.DEB.2.00.1210201837140.28593@uplift.swm.pp.se> <5082E933.60205@gmail.com> <50831CF0.7050106@inria.fr> <50857A63.3030102@gmail.com> <CA+OBy1P-2Hf_uULnnc-KBbpV_Msx_SC6SktdnX1Sr3zsUJ6gKQ@mail.gmail.com> <508BA9C3.9070905@inria.fr> <5092D325.2010605@gmail.com>
Comments: In-reply-to Alexandru Petrescu <alexandru.petrescu@gmail.com> message dated "Thu, 01 Nov 2012 20:53:09 +0100."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 02 Nov 2012 15:59:24 -0400
Message-ID: <14047.1351886364@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 02:01:29 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
    AP> Well yes, the prefix allocated to a vehicle when using NEMO is
    AP> actually DHCPv6 Prefix Delegation RFC6276.  In that RFC the
    AP> presence of HA is mandatory.

    AP> But some times HA may not be available, e.g. in remote areas or
    AP> uncovered areas.  There, one would still want vehicles to
    AP> inter-communicate.

Yes, so if there is no uplink, then there is no addresses, so really,
it's not an address allocation problem, it's a routing problem.

    AP> Direct communication between vehicles in the absence from
    AP> infrastructure is what is being experimented in some settings,
    AP> although I agree they may not be reflected in ISO works.  I can
    AP> speak of the EU project I work on with these V2V and V2V2I
    AP> use-cases.

    >> For the scenario involving the roadside and the vehicle, the
    >> prefix can be exchanged as proposed by Lee
    >> (draft-jhlee-mext-mnpp). The solution from Lee is being
    >> integrated in the ISO TC204 standards related to ISO 21210.

    AP> I am happy to learn that draft-jhlee-mext-mnpp work is
    AP> integrated in ISO TC204 work.

Can you tell us how/if we can view this TC204 work?
Also, I can not find draft-jhlee-mext-mnpp. Is there a typo?

-- 
Michael Richardson
-on the road-