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

Pat Thaler <pat.thaler@broadcom.com> Thu, 23 March 2017 17:29 UTC

Return-Path: <pat.thaler@broadcom.com>
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 A93341294B7 for <int-area@ietfa.amsl.com>; Thu, 23 Mar 2017 10:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
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 mNwkT7BXIobF for <int-area@ietfa.amsl.com>; Thu, 23 Mar 2017 10:29:03 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (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 560FC1252BA for <int-area@ietf.org>; Thu, 23 Mar 2017 10:29:03 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id i34so181787760qtc.0 for <int-area@ietf.org>; Thu, 23 Mar 2017 10:29:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6cmDbVoSgj4z9Kao5pgJ6wh9H0HUEqYn8KU86vLKVW0=; b=dfkzTo9nn04dAnzEPJaQOiKllVElJzXFiIO7LoKg/d7bJePdAVok8wmb1xQo++38Xw Fo0FZ0WVpomqz0/U1OcUA6ALQd8wdZC5aivOKmpOxyuTcltfIEIvq9Ru2tTDuO+m5rVF l2EdlsudfD3Nuq7lhPmvxxn8sY5pM4gUEsSuc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6cmDbVoSgj4z9Kao5pgJ6wh9H0HUEqYn8KU86vLKVW0=; b=hmFZ8q+N62EF//ed/Nr5jVdaseHKYatZrDoPGW+JB1av9buVZ3IUWz+Kj1k0iwWtKU V7d3FtdPzICQsSRGi5aOk5xy7fUkoTZcUTlmkbVAIsaU16PsnnHhSAQoBBROBtjri3QE DDkmB5dOttC23YJYk9R0KC/xHpUGP4r1uF0liKjdhedoIa7AjlblybpjHo+vT8OfLfVx TXTHzOQFgNEroxQjbMp7MDbNQnlUXTugIdkng5tDng52eorCSyfAOR8LAhU1I66B12BA TNUzbbRjPULAYfJB/s2b8A0a+2YWtN2wr0ci/EfnzQk+4+xJgLqVc8EK3YnpsbX/aS/b lgLA==
X-Gm-Message-State: AFeK/H3e8t0NSdekzaZbPk458ZvwbGIsrplYljB8U/rlHrH3Ot19HOMg0ZFd3DY9TLEAlqvc66vwFCV40UBsyG48
X-Received: by 10.237.59.91 with SMTP id q27mr3716715qte.193.1490290142387; Thu, 23 Mar 2017 10:29:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.30.117 with HTTP; Thu, 23 Mar 2017 10:29:01 -0700 (PDT)
In-Reply-To: <b8915ed3-c784-beb4-c946-7f9a9839e759@acm.org>
References: <DB6PR08MB267961B6B492CB9FC98DD011893C0@DB6PR08MB2679.eurprd08.prod.outlook.com> <b8915ed3-c784-beb4-c946-7f9a9839e759@acm.org>
From: Pat Thaler <pat.thaler@broadcom.com>
Date: Thu, 23 Mar 2017 10:29:01 -0700
Message-ID: <CAJt_5EiOrJ=1xPP-LTUfer8rmhPCZx+SvqoUL7tgGd2djeUjWA@mail.gmail.com>
To: Erik Nordmark <nordmark@acm.org>
Cc: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0e773e8cbf8d054b693686
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/FpWVpEUhA8fZtrp9maRd0FJmzXA>
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 17:29:06 -0000

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.


Regads,
Pat



On Wed, Mar 22, 2017 at 6:10 PM, Erik Nordmark <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
>
> 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]
>> *Sent:* March 22, 2017 4:26 AM
>> *To:* statements@ietf.org; Juan Carlos Zuniga
>> <juancarlos.zuniga@sigfox.com>om>; Suresh Krishnan
>> <suresh.krishnan@ericsson.com>om>; Wassim Haddad <wassim.haddad@ericsson.com
>> >
>> *Cc:* Paul Nikolich <paul.nikolich@att.net> (paul.nikolich@att.net)
>> <paul.nikolich@att.net>et>; John Messenger <jmessenger@advaoptical.com>om>;
>> Janos Farkas <Janos.Farkas@ericsson.com>om>; 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>
>>
>> +1-613-963-8141
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>>
>>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>