IETF Logo Mail Archive

Re: [Teas] A question on the definitions of SDP and SAP

mohamed.boucadair@orange.com Mon, 21 March 2022 11:50 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971DC3A126E; Mon, 21 Mar 2022 04:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qhuf14GSlgQP; Mon, 21 Mar 2022 04:50:06 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 C79463A1279; Mon, 21 Mar 2022 04:50:05 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) (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 opfedar25.francetelecom.fr (ESMTP service) with ESMTPS id 4KMXwq4lQnz8sry; Mon, 21 Mar 2022 12:50:03 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1647863403; bh=TbDOBV4F47Wc/UVJteQQNOv+Att6QGwxEdOFwBY+uIs=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=vl8NO7eswjLPl+I361yTFsHgP74tl/rvUKtT8CO5MpXW9jVDdTFnPdm5amEHmZAka gTvomOtAMK6i8O5BGwx2npSwNvlYX9goMlwx3D2Eb21YMCUtR5UPrf1FFEcHUlnfeN kvai+DsKVM9tnz0IiiLTFW+JAbR+VOmr1FGvKjWuWoQLB2x+ux7NoXc+Bx5r032R04 mHFSwmq1TdzlpB34w3X7gEAz46A9NiaKE9kZzlZBflwVq1+HWA+z5mDOwlftdJA2UE XKe4Y1kP9PDD9+5p4VIVxz5tnfRQhRupiNFiVFF8nmTzEqEHlQUSjWb+HAdy3gr+DQ nwJHxPSDtwnbQ==
From: mohamed.boucadair@orange.com
To: Greg Mirsky <gregimirsky@gmail.com>, Adrian Farrel <adrian@olddog.co.uk>, TEAS WG <teas@ietf.org>, opsawg <opsawg@ietf.org>
Thread-Topic: A question on the definitions of SDP and SAP
Thread-Index: AQHYPRVBNwZkEtpVt0O7CSBSp1y4tazJuNBg
Content-Class:
Date: Mon, 21 Mar 2022 11:50:03 +0000
Message-ID: <10787_1647863403_6238666B_10787_254_8_102a93ddc2d248dda598226a48932b5b@orange.com>
References: <CA+RyBmXKneDhX7yELTrhEEL19iL9rATtW_ZSvgceEh6ygP3uYQ@mail.gmail.com>
In-Reply-To: <CA+RyBmXKneDhX7yELTrhEEL19iL9rATtW_ZSvgceEh6ygP3uYQ@mail.gmail.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-03-21T11:47:56Z; 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=836690bd-2579-4553-93e4-d5411d04870a; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_102a93ddc2d248dda598226a48932b5borangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ZZYwGQatALW0uGMQrPR5SAkBTIM>
Subject: Re: [Teas] A question on the definitions of SDP and SAP
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2022 11:50:11 -0000

Hi Greg,

The slice draft already says the following:

      An SDP may be abstracted as a Service Attachment Point (SAP)
      [I-D.ietf-opsawg-sap] for the purpose generalizing the concept
      across multiple service types and representing it in management
      and configuration systems.

Cheers,
Med

De : Greg Mirsky <gregimirsky@gmail.com>
Envoyé : lundi 21 mars 2022 12:17
À : Adrian Farrel <adrian@olddog.co.uk>; TEAS WG <teas@ietf.org>; opsawg <opsawg@ietf.org>; BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Objet : A question on the definitions of SDP and SAP

Hi Adrian,
I've read the draft-ietf-teas-ietf-network-slices<https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/> (many thanks for all your work on it!) and I've got a question. It appears to me that the definition of a Service Demarcation Point section 2.1) as the point of where the IETF Network Slice service is delivered by the provider to a customer is similar to the definition of a Service Attachment Point in draft-ietf-opsawg-sap<https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/> as an "abstraction of the network reference points where network services can be delivered to customers." Hence my question. Is there an intended difference between SDP and SAP that is indicated by using different terms?

Regards,
Greg

_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email