Re: [Int-area] [www.ietf.org/rt #163372] Liaison from IEEE 802.1 WG to IETF IntArea WG

Erik Nordmark <nordmark@sonic.net> Thu, 23 March 2017 18:40 UTC

Return-Path: <nordmark@sonic.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55025129BDA; Thu, 23 Mar 2017 11:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 VLveOU75L4F6; Thu, 23 Mar 2017 11:40:47 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAEFB129407; Thu, 23 Mar 2017 11:40:47 -0700 (PDT)
Received: from [192.168.254.146] (72-172-185-194.bayarea.net [72.172.185.194]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id v2NIegF5016681 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 23 Mar 2017 11:40:43 -0700
To: Pat Thaler <pat.thaler@broadcom.com>, Erik Nordmark <nordmark@acm.org>
References: <DB6PR08MB267961B6B492CB9FC98DD011893C0@DB6PR08MB2679.eurprd08.prod.outlook.com> <b8915ed3-c784-beb4-c946-7f9a9839e759@acm.org> <CAJt_5EiOrJ=1xPP-LTUfer8rmhPCZx+SvqoUL7tgGd2djeUjWA@mail.gmail.com>
Cc: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
From: Erik Nordmark <nordmark@sonic.net>
Message-ID: <1bd9b9fa-3c2c-e476-bdc9-c5add4497c7e@sonic.net>
Date: Thu, 23 Mar 2017 11:40:41 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAJt_5EiOrJ=1xPP-LTUfer8rmhPCZx+SvqoUL7tgGd2djeUjWA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVaBU785qfvmVQOTaYIhWOQH9q/yizxfs6r7pdM9I1rbwEaRX/Mb84seBcahf6XCCX4+NyBw2H+sQWzwj9zYxjmn52bE8VRUvpc=
X-Sonic-ID: C;oM4/OPgP5xGmL9RbNyX4rQ== M;mJzTOPgP5xGmL9RbNyX4rQ==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Kzq5FDYOQdqkneeeN1a6jgB6vKU>
Subject: Re: [Int-area] [www.ietf.org/rt #163372] Liaison from IEEE 802.1 WG to IETF IntArea WG
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 18:40:50 -0000

On 03/23/2017 10:29 AM, Pat Thaler wrote:
> Erik,
>
> The informative annexes explain how to use 802.1Q bridges to implement
> Pfivate VLANs. The capabilities that allow that are covered in the
> normative body of IEEE Std 802.1Q.
>
> The liaison includes suggested text for the ID describing details of
> configuring 802.1Q bridges to accomplish that including references to
> normative parts of 802.1Q.

Pat,

That's great. I initially missed those details in the liaison.

Would it be OK to take that text from the liaison and add it as 
information to the draft? And if so, should I acknowledge anybody in 
particular or just the IEEE 802.1 committee?

Thanks,
     Erik

>
>
>
> On Wed, Mar 22, 2017 at 6:10 PM, Erik Nordmark <nordmark@acm.org
> <mailto:nordmark@acm.org>> wrote:
>
>     On 03/22/2017 02:30 PM, Juan Carlos Zuniga wrote:
>
>         Dear IntArea WG,
>
>
>
>         Please note that we have received the attached liaison letter
>         from the
>         IEEE 802.1 WG with respect to “IP over intentionally partially
>         partitioned links” draft-nordmark-intarea-ippl-05.
>
>
>     I don't see the document listed on
>     http://www.ieee802.org/Communications.shtml#Comm_1703
>     <http://www.ieee802.org/Communications.shtml#Comm_1703>
>
>     Will it be added there so we can refer to it?
>
>
>     Some more detailed comments below:
>
>         1. The tone of the draft should be, "how a router can take
>         advantage of the
>         Asymmetric (Private) VLAN feature offered by 802.1Q bridges."
>
>
>         2. Modifying the section in question to describe how it works,
>         without any
>         conformance language on bridge behavior but explaining 802.1Q
>         standard
>         bridge configuration instead.
>
>
>         3. Make a normative reference to 802.1Q.
>
>
>     My bad; I thought I already had it as a reference.
>     However, I'm not sure it can be normative since both annex B and
>     annex F are marked as informational in 802.1Q-1998. It wasn't clear
>     to me that there is sufficient material in the normative parts of
>     802.1Q-1998 to describe the required behaviors for promiscuous,
>     community, and isolated ports.
>
>     If the 802.1 group is asserting that all of those behaviors are
>     (optional) parts of the 802.1Q-1998 standard it would be helpful to
>     know that.
>
>     In addition, if possible, also to have more specific references to
>     normative sections in 802.1Q which describe this behavior.
>
>     We'd still need some explanatory text in the draft to map between
>     the 802.1Q terminology and the "promiscuous, community, isolated"
>     terminology that is used in industry. Before seeing the test I can't
>     tell whether such text would need to have RFc2119 terms to describe
>     the mapping. However, I don't think that would be a constraints on
>     bridge implementations but instead statements of the form "for the
>     purposes if running IP over 802.1Q we assume that
>     promisc/community/isolated ports are configured as follows using the
>     802.1Q asymetric VLAN standard...
>
>     But that is predicated on the all the necessary "private VLAN"
>     behaviors being part of the IEEE 802.1Q-1998 standard. So I'd be
>     greatful for clarifications on that point before I start editing the
>     draft.
>
>
>     Thanks,
>         Erik
>
>
>
>         If you have any comments, please send them to the list.
>
>
>
>         We will also allocate some time for to discuss about this during our
>         meeting in Chicago.
>
>
>
>         Best,
>
>
>
>         Juan-Carlos & Wassim
>
>         (IntArea WG co-chairs)
>
>
>
>
>
>         *From:*Glenn Parsons [mailto:glenn.parsons@ericsson.com
>         <mailto:glenn.parsons@ericsson.com>]
>         *Sent:* March 22, 2017 4:26 AM
>         *To:* statements@ietf.org <mailto:statements@ietf.org>; Juan
>         Carlos Zuniga
>         <juancarlos.zuniga@sigfox.com
>         <mailto:juancarlos.zuniga@sigfox.com>>; Suresh Krishnan
>         <suresh.krishnan@ericsson.com
>         <mailto:suresh.krishnan@ericsson.com>>; Wassim Haddad
>         <wassim.haddad@ericsson.com <mailto:wassim.haddad@ericsson.com>>
>         *Cc:* Paul Nikolich <paul.nikolich@att.net
>         <mailto:paul.nikolich@att.net>> (paul.nikolich@att.net
>         <mailto:paul.nikolich@att.net>)
>         <paul.nikolich@att.net <mailto:paul.nikolich@att.net>>; John
>         Messenger <jmessenger@advaoptical.com
>         <mailto:jmessenger@advaoptical.com>>;
>         Janos Farkas <Janos.Farkas@ericsson.com
>         <mailto:Janos.Farkas@ericsson.com>>; pat.thaler@broadcom.com
>         <mailto:pat.thaler@broadcom.com>
>         *Subject:* Liaison from IEEE 802.1 WG to IETF IntArea WG
>
>
>
>         Please find attached a liaison from the IEEE 802.1 WG.
>
>
>
>         I will be available to present this during the  IntArea WG meeting.
>         This is in regards to your agenda item #4.
>
>
>
>         Cheers,
>
>         Glenn.
>
>
>
>
>
>         --
>
>         Glenn Parsons - Chair, IEEE 802.1
>
>         glenn.parsons@ericsson.com <mailto:glenn.parsons@ericsson.com>
>         <mailto:glenn.parsons@ericsson.com
>         <mailto:glenn.parsons@ericsson.com>>
>
>         +1-613-963-8141 <tel:%2B1-613-963-8141>
>
>
>
>
>
>
>
>         _______________________________________________
>         Int-area mailing list
>         Int-area@ietf.org <mailto:Int-area@ietf.org>
>         https://www.ietf.org/mailman/listinfo/int-area
>         <https://www.ietf.org/mailman/listinfo/int-area>
>
>
>     _______________________________________________
>     Int-area mailing list
>     Int-area@ietf.org <mailto:Int-area@ietf.org>
>     https://www.ietf.org/mailman/listinfo/int-area
>     <https://www.ietf.org/mailman/listinfo/int-area>
>
>