Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34
Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 08 April 2019 09:01 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1EBD120099; Mon, 8 Apr 2019 02:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJRQ9Vqz-N1e; Mon, 8 Apr 2019 02:01:32 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8244812006D; Mon, 8 Apr 2019 02:01:32 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3891RXs150869; Mon, 8 Apr 2019 11:01:27 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 15847203806; Mon, 8 Apr 2019 11:01:27 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 007EF20378F; Mon, 8 Apr 2019 11:01:26 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3891QlQ022734; Mon, 8 Apr 2019 11:01:26 +0200
To: Pascal Thubert <pthubert@cisco.com>, int-dir@ietf.org
Cc: ietf@ietf.org, its@ietf.org, draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <a8aad636-069c-4451-dbf1-72c1db2204ef@gmail.com>
Date: Mon, 08 Apr 2019 11:01:26 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <155169869045.5118.3508360720339540639@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------390F6E57EC4863E06DD9FE6D"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/19Q9WQyQRLi6ARE1q651aLAnkSA>
Subject: Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 09:01:36 -0000
As a note: please improve the title of this. It is not an early review. It is a late review. There have been several reviews of this document until here, and two shepherd reviews. Alex Le 04/03/2019 à 12:24, Pascal Thubert a écrit : > Reviewer: Pascal Thubert > Review result: Not Ready > > Reviewer: Pascal Thubert > Review result: Not ready. Need to clarify IEEE relationship, IOW which SDO > defines the use of L2 fields, what this spec enforces vs. recognizes as being > used that way based on IEEE work. The use of IPv6 ND requires a lot more > thoughts, recommendation to use 6LoWPAN ND. The definition of a subnet is > unclear. It seems that RSUs would have prefixes but that is not discussed. > > I am an assigned INT and IOT directorates reviewer for < > draft-ietf-ipwave-ipv6-over-80211ocb-34 >. These comments were written > primarily for the benefit of the Internet Area Directors. Document editors and > shepherd(s) should treat these comments just like they would treat comments > from any other IETF contributors and resolve them along with any other Last > Call comments that have been received. For more details on the INT Directorate, > see https://datatracker.ietf.org/group/intdir/about/ > > Majors issues > ----------------- > > “ > > o Exceptions due to different operation of IPv6 network layer on > 802.11 than on Ethernet. > > “ > Is this doc scoped to OCB or 802.11 in general? Is there an expectation that an > implementer of IPv6 over Wi-Fi refers to this doc? Spelled as above, it seems > that you are defining the LLC. Figure 1 shows the proposed adaptation layer as > IEEE LLC work. Who defines those fields, IETF or IEEE, or mixed? Who defines > their use? If this spec defines a new LLC header (vs. how to use an IEEE field) > then it should be very clear, and the newly defined fields should be isolated > from IEEE fields. > > " > The IPv6 packet transmitted on 802.11-OCB MUST be immediately > preceded by a Logical Link Control (LLC) header and an 802.11 header. > > " > Is there anything new or specific to OCB vs. classical 802.11 operations? > If/when this is echoing the IEEE specs then this text should not use uppercase > but say something like: 'Per IEEE Std 802.11, the IPv6 packet transmitted on > 802.11-OCB is immediately preceded by a Logical Link Control (LLC) header and > an 802.11 header ...' > > different things? Why define both? > > " An 'adaptation' layer is inserted between a MAC layer and the > Networking layer. This is used to transform some parameters between > their form expected by the IP stack and the form provided by the MAC > layer. > " > Is this different from what an AP does when it bridges Wi-Fi to Ethernet? Is > this IETF business? > > " > The Receiver and Transmitter Address fields in the 802.11 header MUST > contain the same values as the Destination and the Source Address > fields in the Ethernet II Header, respectively. > " > Same, this is IEEE game isn't it? > > " > > Solutions for these problems SHOULD > consider the OCB mode of operation. > " > This is not specific enough to be actionable. I suggest to remove this sentence. > It would be of interest for the people defining those solutions to understand > the specific needs of OCB vs. Wi Fi, but I do not see text about that. > > " > > The method of forming IIDs > described in section 4 of [RFC2464] MAY be used during transition > time. > " > Contradicts section 4.3 that says > " > Among these types of > addresses only the IPv6 link-local addresses MAY be formed using an > EUI-64 identifier. > " > > " > > This > subnet MUST use at least the link-local prefix fe80::/10 and the > interfaces MUST be assigned IPv6 addresses of type link-local. > " > If this is conforming IPv6 then the MUST is not needed. > > " > A subnet is formed by the external 802.11-OCB interfaces of vehicles > that are in close range (not by their in-vehicle interfaces). > " > Is the definition transitive? Do we really get a subnet? > A is close to B who is close to C .... to Z, makes Paris one subnet! Are you > talking about a link, rather? > > " > The Neighbor Discovery protocol (ND) [RFC4861] MUST be used over > 802.11-OCB links. > " > > IPv6 ND is not suited for a non-broadcast network. How does DAD work? > Maybe you could consider RFC 6775 / RFC 8505 instead. > > " > In the moment the MAC address is changed > on an 802.11-OCB interface all the Interface Identifiers of IPv6 > addresses assigned to that interface MUST change. > " > Why is that? This is unexpected, and hopefully wrong. > > Minor issues > --------------- > > " OCB (outside the context of a basic service set - BSS): A mode of > operation in which a STA is not a member of a BSS and does not > utilize IEEE Std 802.11 authentication, association, or data > confidentiality. > > 802.11-OCB: mode specified in IEEE Std 802.11-2016 when the MIB > attribute dot11OCBActivited is true. Note: compliance with standards > and regulations set in different countries when using the 5.9GHz > frequency band is required. > " > > Are these 2 different things? > > " > Among these types of > addresses only the IPv6 link-local addresses MAY be formed using an > EUI-64 identifier. > " > This text should not be in a LL specific section since it deals with the other > addresses. Maybe rename the section to "addressing" or something? > > " > For privacy, the link-local address MAY be formed according to the > mechanisms described in Section 5.2. > " > The MAY is not helpful. I suggest to remove the sentence that does not bring > value vs. 5.2 > > Could you make sections 4.3 and 4.5 contiguous? > > " > If semantically > opaque Interface Identifiers are needed, a potential method for > generating semantically opaque Interface Identifiers with IPv6 > Stateless Address Autoconfiguration is given in [RFC7217]. > > Semantically opaque Interface Identifiers, instead of meaningful > Interface Identifiers derived from a valid and meaningful MAC address > ([RFC2464], section 4), MAY be needed in order to avoid certain > privacy risks. > > ... > > In order to avoid these risks, opaque Interface Identifiers MAY be > formed according to rules described in [RFC7217]. These opaque > Interface Identifiers are formed starting from identifiers different > than the MAC addresses, and from cryptographically strong material. > Thus, privacy sensitive information is absent from Interface IDs, and > it is impossible to calculate the initial value from which the > Interface ID was calculated. > > " > Duplicate and mis ordered text, isn't it? > > " For this reason, an attacker may realize many > attacks on privacy. > " > Do we attack privacy? Maybe say that privacy is a real concern, and maybe move > that text to security section? > > " > The way Interface Identifiers are used MAY involve risks to privacy, > as described in Section 5.1. > " > Also duplicate > > Nits > ------ > > " > IP packets MUST be transmitted over 802.11-OCB media as QoS Data > frames whose format is specified in IEEE Std 802.11. > " > Please add link to the reference > > " the 802.11 hidden node" > Do not use 802.11 standalone (multiple occurrences). > => "the IEEE Std. 802.11 [ ref ] hidden node", or just "the hidden terminal". > > BCP 14 text: > > Suggest to use this text: > “ > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and > "OPTIONAL" in this document are to be interpreted as described in > https://tools.ietf.org/html/bcp14 https://tools.ietf.org/html/bcp14 > [https://tools.ietf.org/html/rfc2119][RFC8174] when, and only when, they > appear in all capitals, as shown here. > > “ > > All the best > > Pascal > > >
- [Int-dir] Intdir early review of draft-ietf-ipwav… Pascal Thubert
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre PETRESCU
- Re: [Int-dir] [ipwave] Intdir early review of dra… Abdussalam Baryun
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… NABIL BENAMAR
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Joel M. Halpern
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Carsten Bormann
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] [ipwave] Intdir early review of dra… Charlie Perkins
- Re: [Int-dir] [ipwave] Intdir early review of dra… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Rob Wilton (rwilton)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Brian E Carpenter
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… 神明達哉
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… 神明達哉
- Re: [Int-dir] Intdir early review of draft-ietf-i… Brian E Carpenter
- Re: [Int-dir] Intdir early review of draft-ietf-i… Ole Troan
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Ole Troan
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Ole Troan
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Ole Troan
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… NABIL BENAMAR
- Re: [Int-dir] Intdir early review of draft-ietf-i… Ole Troan
- Re: [Int-dir] Intdir early review of draft-ietf-i… 神明達哉
- Re: [Int-dir] Intdir early review of draft-ietf-i… 神明達哉
- Re: [Int-dir] [ipwave] Intdir early review of dra… Abdussalam Baryun
- Re: [Int-dir] Intdir early review of draft-ietf-i… Brian E Carpenter
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre PETRESCU
- Re: [Int-dir] Intdir early review of draft-ietf-i… Ole Troan
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- [Int-dir] IPv6-over-foo and Addressing Architectu… Suresh Krishnan
- Re: [Int-dir] IPv6-over-foo and Addressing Archit… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] [ipwave] Intdir early review of dra… William Whyte
- Re: [Int-dir] Intdir early review of draft-ietf-i… 神明達哉
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] [ipwave] Intdir early review of dra… Alexandre Petrescu
- Re: [Int-dir] about V2I to traffic lights control… Alexandre Petrescu
- Re: [Int-dir] [ipwave] Intdir early review of dra… Brian E Carpenter
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] Intdir early review of draft-ietf-i… Pascal Thubert (pthubert)
- Re: [Int-dir] [ipwave] Intdir early review of dra… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] Intdir early review of draft-ietf-i… Alexandre Petrescu
- Re: [Int-dir] [ipwave] Intdir early review of dra… Abdussalam Baryun
- Re: [Int-dir] [ipwave] Intdir early review of dra… Abdussalam Baryun
- Re: [Int-dir] [ipwave] Intdir early review of dra… NABIL BENAMAR
- Re: [Int-dir] [ipwave] Intdir early review of dra… Nabil Benamar
- Re: [Int-dir] [ipwave] Intdir early review of dra… Sri Gundavelli (sgundave)
- Re: [Int-dir] [ipwave] Intdir early review of dra… NABIL BENAMAR
- Re: [Int-dir] [ipwave] Intdir early review of dra… Sri Gundavelli (sgundave)
- Re: [Int-dir] [ipwave] Intdir early review of dra… Alexandre Petrescu
- Re: [Int-dir] [ipwave] Intdir early review of dra… Alexandre Petrescu
- [Int-dir] link-local text (Re: Intdir early revie… 神明達哉
- Re: [Int-dir] [ipwave] Intdir early review of dra… Brian E Carpenter
- Re: [Int-dir] [ipwave] Intdir early review of dra… Brian E Carpenter
- Re: [Int-dir] [ipwave] Intdir early review of dra… Abdussalam Baryun
- Re: [Int-dir] [ipwave] Intdir early review of dra… Sri Gundavelli (sgundave)
- Re: [Int-dir] [ipwave] Intdir early review of dra… NABIL BENAMAR
- Re: [Int-dir] [ipwave] Intdir early review of dra… Brian E Carpenter
- Re: [Int-dir] [ipwave] Intdir early review of dra… Nabil Benamar
- Re: [Int-dir] [ipwave] Intdir early review of dra… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] link-local text (Re: Intdir early r… Alexandre Petrescu
- Re: [Int-dir] link-local text (Re: Intdir early r… Alexandre Petrescu
- Re: [Int-dir] link-local text (Re: Intdir early r… Brian E Carpenter
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Brian E Carpenter
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Pascal Thubert (pthubert)
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Pascal Thubert (pthubert)
- Re: [Int-dir] [ipwave] Intdir early review of dra… Jong-Hyouk Lee
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] pencil and paper vs cars Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] link-local text (Re: Intdir early r… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] Expertise on ND problems on OCB Alexandre Petrescu
- Re: [Int-dir] [ipwave] Expertise on ND problems o… Charlie Perkins
- Re: [Int-dir] link-local text (Re: Intdir early r… 神明達哉
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… 神明達哉
- Re: [Int-dir] link-local text (Re: Intdir early r… Pascal Thubert (pthubert)
- Re: [Int-dir] link-local text (Re: Intdir early r… Brian E Carpenter
- Re: [Int-dir] link-local text (Re: Intdir early r… 神明達哉
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Brian E Carpenter
- [Int-dir] draft-ietf-ipwave-ipv6-over-80211ocb an… Brian E Carpenter
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Sri Gundavelli (sgundave)
- Re: [Int-dir] which BSM? Alexandre Petrescu
- Re: [Int-dir] link-local text (Re: Intdir early r… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Pascal Thubert (pthubert)
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… Alexandre Petrescu
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] link-local text (Re: Intdir early r… Alexandre Petrescu
- Re: [Int-dir] ND-over-OCB hidden terminals: truck… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… 神明達哉
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… Alexandre Petrescu
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… 神明達哉
- Re: [Int-dir] link-local text (Re: Intdir early r… 神明達哉
- Re: [Int-dir] 118 神明達哉
- Re: [Int-dir] 118 Brian E Carpenter
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] use-cases in Problem Statement Alexandre Petrescu
- Re: [Int-dir] use-cases in Problem Statement NABIL BENAMAR
- Re: [Int-dir] 118 Joel M. Halpern
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] 118 Eric Gray
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… 神明達哉
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] 118 Stephen Farrell
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… Alexandre Petrescu
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… 神明達哉
- Re: [Int-dir] 118 Joel M. Halpern
- Re: [Int-dir] 118 神明達哉
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Brian E Carpenter
- Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1… Alexandre Petrescu
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Alexandre Petrescu
- Re: [Int-dir] 118 神明達哉
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] draft-ietf-ipwave-ipv6-over-80211oc… Brian E Carpenter
- Re: [Int-dir] 118 神明達哉
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] 118 神明達哉
- Re: [Int-dir] 118 Suresh Krishnan
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] 118 神明達哉
- Re: [Int-dir] 118 Alexandre Petrescu
- Re: [Int-dir] [ipwave] Expertise on ND problems o… Carsten Bormann
- Re: [Int-dir] [ipwave] Expertise on ND problems o… Pascal Thubert (pthubert)
- Re: [Int-dir] [ipwave] Expertise on ND problems o… Sri Gundavelli (sgundave)