Re: [OPSAWG] WG LC: draft-ietf-opsawg-sap

mohamed.boucadair@orange.com Wed, 18 May 2022 15:05 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE1AC157B40 for <opsawg@ietfa.amsl.com>; Wed, 18 May 2022 08:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNPAaiYLbdAI for <opsawg@ietfa.amsl.com>; Wed, 18 May 2022 08:05:41 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253C2C159480 for <opsawg@ietf.org>; Wed, 18 May 2022 08:05:21 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4L3GWL6P8Hz7v3t; Wed, 18 May 2022 17:05:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1652886318; bh=dkaQOh8kCSdVw/3tpCUJUlJplaUPQziG4PzqTZhLXfs=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=hbkS6fTJkJU29Bl6RaoJCjiSwHFlr/713+6j/or8xAPx7XiqMW1/P5RuvhCKIUkEV /UdZr6RKcAJ67OM5o0Wwe0xP8VUTesefOPfI9afWBlE8fDs0xNB75x9GDVo0fcEXlR gasWMxXxhXF5nA+tKaTYNrt0S4ZwgvGNcOBZpbICnpM5j+Ao9+kMBnkKM0xQbcNSzo Es1Cqpy02zVGQxbmiWrtGm00zjc1+wBMM8+X/mAoQS+ywpSoI2sfLCA6R+u4topwUF tJ3464dxkfuEpblFn9EC+EkOo6dL+HhgU6p8rgjFUJExsE5PK2YeZyx/9QSWfHkkW1 DtMHmlJrWx6UA==
From: mohamed.boucadair@orange.com
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] WG LC: draft-ietf-opsawg-sap
Thread-Index: AQHYVns1bP7wpHesBUGkEs4KoGeiH60k485g
Content-Class:
Date: Wed, 18 May 2022 15:05:18 +0000
Message-ID: <27985_1652886318_62850B2E_27985_314_2_d0aa475c8eab4013be93140119f3657c@orange.com>
References: <CH0PR11MB536478F636F61BF2300A87C0B8F79@CH0PR11MB5364.namprd11.prod.outlook.com> <BN9PR11MB537168D93A288A869526F6AFB8CE9@BN9PR11MB5371.namprd11.prod.outlook.com> <AM7PR07MB6248B1969F8E6F2D47BDB32FA0D19@AM7PR07MB6248.eurprd07.prod.outlook.com> <BN9PR11MB537150C0A68F6B5C508D425DB8D19@BN9PR11MB5371.namprd11.prod.outlook.com> <12853_1652881793_6284F981_12853_103_10_3cff5791b2e84b52a8f10f41bb87dad2@orange.com> <BN9PR11MB537185A536341CAF1467E6E8B8D19@BN9PR11MB5371.namprd11.prod.outlook.com>
In-Reply-To: <BN9PR11MB537185A536341CAF1467E6E8B8D19@BN9PR11MB5371.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-05-18T15:04:01Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=4681ba81-0875-4dae-a31e-0fdebac10230; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.50]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/TcHCon1KfbhVr5rd-hk0sLMDwUU>
Subject: Re: [OPSAWG] WG LC: draft-ietf-opsawg-sap
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2022 15:05:45 -0000

Re,

Thanks Joe for sharing your thoughts. 

A new entry appears now in -06: https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-sap-06

Cheers,
Med

> -----Message d'origine-----
> De : Joe Clarke (jclarke) <jclarke@cisco.com>
> Envoyé : mercredi 18 mai 2022 16:47
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc : opsawg@ietf.org
> Objet : Re: [OPSAWG] WG LC: draft-ietf-opsawg-sap
> 
> On 5/18/22 09:50, mohamed.boucadair@orange.com wrote:
> > Hi Joe,
> >
> > FWIW, rfc4026#section-6.1 defines AC as follows:
> >
> > ==
> > 6.1.  Attachment Circuit (AC)
> >
> >    In a Layer 2 VPN the CE is attached to PE via an Attachment
> Circuit
> >    (AC).  The AC may be a physical or logical link.
> > ==
> >
> > which we can generalize as:
> >
> > ==
> > 6.1.  Attachment Circuit (AC)
> >
> >    The CE is attached to PE via an Attachment Circuit
> >    (AC).  The AC may be a physical or logical link.
> > ==
> >
> > We don't have an entry for AC because we thought that the
> meaning is already conveyed in the CE/PE entries:
> >
> > ==
> >    Customer Edge (CE):  An equipment that is dedicated to a
> particular
> >       customer and is directly connected to one or more Provider
> Edges
> >       (PEs) via attachment circuits (ACs)...
> >
> >    Provider Edge (PE):  An equipment owned and managed by the
> service
> >       provider that can support multiple services (e.g., VPNs)
> for
> >       different customers.  A PE is directly connected to one or
> more
> >       CEs via ACs.
> > ==
> >
> > Please let us know if you still prefer having the entry added.
> Thanks.
> 
> It was this above I was "spot-reading" to see how you had changed
> the text to clarify SAP.  When I saw "AC" I had expected to see it
> called out in terminology like PE is.  I did find it as you show,
> but I still thought it, being referenced in other places like
> PE/CE, and in 6.1 would necessitate a separate terminology entry.
> 
> Joe


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.