Re: Comments on draft-ietf-6man-default-iids-01.txt

[Alexandru Petrescu <[e-mail]>]

Le 24/11/2014 20:39, Ralph Droms a écrit :
>
> On Nov 24, 2014, at 2:09 PM 11/24/14, Brian E Carpenter
> <[e-mail]> wrote:
>
>> On 25/11/2014 00:34, Ole Troan wrote:
>>> Ralph,
>>>
>>>>> [...] as far as I can see IPv6 over PPP is no different that
>>>>> IPv6 over any other multicast capable link-layer.
>>>> Ole - In your opinion, does draft-ietf-6man-default-iids-01.txt
>>>> give enough detail as written to be applied as an update to RFC
>>>> 5072?
>>>
>>> I don't know. I think we need to wait for an update of the draft
>>> with the changes discussed at the meeting.
>>>
>>> then we need to look at the set of IPv6 over foo documents and
>>> decide if and what updates are required.
>>
>> As a reminder, we already attempted to catalogue those documents
>> in http://tools.ietf.org/html/draft-ietf-6man-why64-08#section-4.1
>> , paragraph 3. We found 14 RFCs and 4 drafts.
>
> Looks like there is pretty good overlap between the list of
> IPv6-over-foo documents in draft-ietf-6man-why64 and the list of RFCs
> updated by draft-ietf-6man-default-iids.  Authors of the two
> documents might want to coordinate their lists (I understand the
> lists won't necessarily match exactly).

Right, the why64 list does not contain 2491 NBMA, 3572 MAPOS, 4391 
Infiniband cited by the default-iids; the list in this latter does not 
cite 4944 802.15.4, 2529 6over4, 5214 ISATAP cited by why64.

I didnt know IPv6-over-MAPOS and -Infiniband existed.  I wonder to what 
extent are they or have they been used.

> These two documents listed in draft-ietf-6man-why64 -
> draft-brandt-6man-lowpanz-02 and draft-ietf-6man-6lobac-01 - have
> moved to 6lo, draft-ietf-6lo-lowpanz-08 and draft-ietf-6lo-6lobac-00,
> respectively.
>
> If draft-ietf-6man-default-iids is published as an RFC, I assume
> documents published after that publication will be updated to reflect
> its requirements and we'll want to manage those affected drafts that
> are in process to make sure they coordinate with
> draft-ietf-6man-default-iids.

I agree.  Similarly, recommendation in default-iids mayneed to influence 
a number of _individual proposal_ drafts IPv6-over-foo like 
draft-hong-6lo-ipv6-over-nfc-02 or draft-petrescu-ipv6-over-80211p-02.

Alex

>
> - Ralph
>
>
>>
>> Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list [e-mail] Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>