IETF Logo Mail Archive

Re: [sfc] RFC 8677 (Name-Based Service Function Forwarder (nSFF) Component within a SFC Framework) published

Dirk Trossen <Dirk.Trossen@InterDigital.com> Thu, 21 November 2019 08:43 UTC

Return-Path: <Dirk.Trossen@InterDigital.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8518A120989 for <sfc@ietfa.amsl.com>; Thu, 21 Nov 2019 00:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_MSPIKE_H2=-0.001, 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=interdigital.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 6y7hTIDkZuY5 for <sfc@ietfa.amsl.com>; Thu, 21 Nov 2019 00:43:27 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770100.outbound.protection.outlook.com [40.107.77.100]) (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 94F71120801 for <sfc@ietf.org>; Thu, 21 Nov 2019 00:43:27 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LjXzKtVjUtp/LsqLcGfwlXziN/YozQt2Glu7RgJT1TUkVEw2VQICYv0ZAvX4+vVeii3sZRrQVIUj3vIw3zp9z/R5pBlW5A186xLsRv2LKpcFcAz4BZn1AyEMeD2odV6MAztBMfs42gQ5OyQF6kXn3pn6tYdwlSIpJJTdvFuhZ4U30ZRxowR7b8NHwrTWJ+/Px13cL3hj3cZS8gnBLzDm/2hPx+l77yWTFrJqcXj5bUAUi1cdMlRvSlais88u20K+9qaJrjVo6QPU2TzNo8Fv6zcTFH7kQC01JFFNIjU2P4xbo5G8Di/g7bNGKeqnhjRXMUIakB5AguzK9h/07XlgkQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=08q54agFwknadMfYDlBypRNKlKHHqayFjHIKvggP+5w=; b=a5ChjxHY0gM/pZtbqPYW3M/8BSKxkd2HicIFu/8FE8tFAsohAxrfhF3K3ixhecWRlO1hTkXO8LHirkXgOznd+250xjvZSXPkMVl1+tEnPkw8ZO6nah9/9z5uX/nEtTXwyeqgqvdFpxeLbWMHhJr14Anz6s4847yaNIuLVShVUbPDB7oRXvpCCvSz2SnCmCyJBE/R0zjBb+8gToQXsftCjsswmAXa38bVI2rDEYCKyqu1NSy1Ex2kNHk5X/eGzYTCBJcxEJDWETOS1RNZ/OPAigAHq4LET9yg3DcjXZuq15v5gq+RHACBpMDdAXChLj9Z9x1Eka0IMQIjOooz4RaAXg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=interdigital.com; dmarc=pass action=none header.from=interdigital.com; dkim=pass header.d=interdigital.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interdigital.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=08q54agFwknadMfYDlBypRNKlKHHqayFjHIKvggP+5w=; b=iidODS7yS1tUrX5ss6FdPYXSe9b1sGvVIUfS2V8VCyWYJcbI0B+fbgkdPS3Qfwl3RA8vxuAwef/Wkv4qmQWLtzIPX0KTTufbGqY6p+8leK9vvIjnGR3E78o7eiWyeLgSjWMcQG25V4oEH8imyuhrfqBIad0irJAD/7q1AsngE/I=
Received: from MN2PR10MB3695.namprd10.prod.outlook.com (20.179.85.138) by MN2PR10MB3136.namprd10.prod.outlook.com (20.179.144.206) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.17; Thu, 21 Nov 2019 08:43:24 +0000
Received: from MN2PR10MB3695.namprd10.prod.outlook.com ([fe80::dd66:6c14:7c63:d42b]) by MN2PR10MB3695.namprd10.prod.outlook.com ([fe80::dd66:6c14:7c63:d42b%3]) with mapi id 15.20.2474.018; Thu, 21 Nov 2019 08:43:24 +0000
From: Dirk Trossen <Dirk.Trossen@InterDigital.com>
To: Davey Song <songlinjian@gmail.com>, Akbar Rahman <Akbar.Rahman@InterDigital.com>
CC: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] RFC 8677 (Name-Based Service Function Forwarder (nSFF) Component within a SFC Framework) published
Thread-Index: AdWgEbLgnWVV+s+yQKuEoWc8CWfVxwAEDFMAAAlpbJA=
Date: Thu, 21 Nov 2019 08:43:24 +0000
Message-ID: <MN2PR10MB3695D539D077B31407784BF6F34E0@MN2PR10MB3695.namprd10.prod.outlook.com>
References: <DM6PR10MB34184E50D2A25CA45EB84941E74E0@DM6PR10MB3418.namprd10.prod.outlook.com> <CAAObRXL+ydM=hAZUgXEJvocBk0GFPG6Fpa7xdog_Ns9Q1TL0Hg@mail.gmail.com>
In-Reply-To: <CAAObRXL+ydM=hAZUgXEJvocBk0GFPG6Fpa7xdog_Ns9Q1TL0Hg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.Trossen@InterDigital.com;
x-originating-ip: [185.65.26.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1dfac60b-a7d7-449d-f584-08d76e5edf2d
x-ms-traffictypediagnostic: MN2PR10MB3136:|MN2PR10MB3136:
x-ms-exchange-purlcount: 2
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR10MB3136B769C85385D3B2B2E90AF34E0@MN2PR10MB3136.namprd10.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0228DDDDD7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(39830400003)(136003)(366004)(396003)(346002)(189003)(199004)(51914003)(76176011)(478600001)(86362001)(14454004)(606006)(316002)(54896002)(71190400001)(6306002)(236005)(790700001)(6116002)(71200400001)(66476007)(186003)(66446008)(6246003)(966005)(66946007)(76116006)(8676002)(4326008)(11346002)(99286004)(110136005)(446003)(54906003)(229853002)(66556008)(33656002)(7696005)(102836004)(6436002)(26005)(5660300002)(55016002)(52536014)(64756008)(25786009)(6636002)(2906002)(256004)(14444005)(74316002)(7736002)(6506007)(9686003)(3846002)(8936002)(66066001)(9326002)(81166006)(53546011)(81156014)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR10MB3136; H:MN2PR10MB3695.namprd10.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: InterDigital.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: eWUplD4u4p0WYOsLPgpzLB6GqnAgyZKGLk0VqCI0ZehBDrlfpiRW859do0Taro+f3gWwXglXG9ToN/yv+ttj01AkaVboQDwS5dgEdqrZryMgV+2TKglIvSZY1HXiJYRZG5q+u9fIEcWAMQdoozCz3V9efvnELxTs/PqavpRGyTP7w5y9zDtBu6NMz8MaMOPJ7mO6hcPIkurKYBVlbB8FJsO2Po9D5+PnMClZu1hgKaGGWilPNW3YzpbhovluJElYEpIA7FLDQ2O3nLrbHNKhvnZFxqhnIuL3JoR3ZsT5TAnb19sf+dUvXMDwS1UKSH/KXFtJDZAbdbNFqWGsS3EPOFr0Yukz/bibRPRqZhMcYl3gh3Gvb3Pb3M8cdje2iYupfbspsM45f9aIFmWk8J5LYkLcod9F/CMVz1bwNkxyAm+97o4fgRBNjJ+ecXIcKkvB1P0kC1SOqSb9dpWjibIU9a0IHVnC1Arj4UbvUbzLLRU=
Content-Type: multipart/alternative; boundary="_000_MN2PR10MB3695D539D077B31407784BF6F34E0MN2PR10MB3695namp_"
MIME-Version: 1.0
X-OriginatorOrg: interdigital.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1dfac60b-a7d7-449d-f584-08d76e5edf2d
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2019 08:43:24.4967 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e351b779-f6d5-4e50-8568-80e922d180ae
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tegoCEgzFIfotHq9mKfhumV70867sP7jbDvqTGDUW/HZsd0PV8r2U4OTF6c87nDBL+Js6alRn7wNPsATuxXAIo7mqy2xe96Jxae1S4Jahis=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR10MB3136
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/o5LOfMyhq56JFw3OPpzopNQHFcw>
Subject: Re: [sfc] RFC 8677 (Name-Based Service Function Forwarder (nSFF) Component within a SFC Framework) published
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 08:43:31 -0000

Hi Davey,

Thanks for the email. As we outline in the document, alongside a 5G use case, we don’t see DNS as being suitable for the dynamic changes in the relationships, often realized virtualized and dynamically spun up albeit distributed named entities.

Best,

Dirk

From: sfc <sfc-bounces@ietf.org> On Behalf Of Davey Song
Sent: 21 November 2019 04:13
To: Akbar Rahman <Akbar.Rahman@InterDigital.com>
Cc: Joel M. Halpern <jmh@joelhalpern.com>; sfc@ietf.org
Subject: Re: [sfc] RFC 8677 (Name-Based Service Function Forwarder (nSFF) Component within a SFC Framework) published

Hi Akbar,

I just notice this RFC document. I did not quite follow the topic, but according to the title, if you want to name a service and change dynamically instead of L2/L3 address, why not using DNS for this purpose?

Best Regards,
Davey

On Thu, 21 Nov 2019 at 10:17, Akbar Rahman <Akbar.Rahman@interdigital.com<mailto:Akbar.Rahman@interdigital.com>> wrote:
Hi Joel (& WG)


FYI – Our draft that initially started in the SFC WG, and then proceeded to the ISE route (with your guidance), has now been published as an RFC:


  *   RFC 8677 - Name-Based Service Function Forwarder (nSFF) Component within a SFC Framework

     *   https://tools.ietf.org/html/rfc8677


We would be happy to respond to any comments or feedback from the WG.


Best Regards,


Akbar
_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email