IETF Logo Mail Archive

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

Davey Song <songlinjian@gmail.com> Thu, 21 November 2019 04:12 UTC

Return-Path: <songlinjian@gmail.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 E30C91208AF for <sfc@ietfa.amsl.com>; Wed, 20 Nov 2019 20:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 o37F--kIMjbB for <sfc@ietfa.amsl.com>; Wed, 20 Nov 2019 20:12:42 -0800 (PST)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 6B138120220 for <sfc@ietf.org>; Wed, 20 Nov 2019 20:12:42 -0800 (PST)
Received: by mail-qt1-x833.google.com with SMTP id y39so2244974qty.0 for <sfc@ietf.org>; Wed, 20 Nov 2019 20:12:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RPztJZb7A/jLHV/LcbvOf9plhoGcfzTyRPTu8ss29lc=; b=HKmNP8TeI+/bbLYlngLvYJBRPledDSvFsnkJKVAfXMYRj2coN9egUn+OZCYni4pMCg R/apWw7Y2NeQEnTYziW3J5RWGfzJqQq31jObfCnSOBaI+tSFv/FNnx1SzJs32acUnMeZ Pu8YMUnmVFybEbucUkHfCroRSIyQGxXGr/P/8dT6k7dokhDLYG3Hd2d8JzSUy3+Wa4a+ xrtXhgrV86JY9YmcIv7o1qKhj1uXglmDpRCUpOMU6SS4044HIJG3Q5dwmcOYOz8vGrJP j5o9YX8E2wynd0TSsJ2BWMMglFzz0y51c76dWzmgiq9zisdnN1mIst1/BlM+eZZtOPfu 8axQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RPztJZb7A/jLHV/LcbvOf9plhoGcfzTyRPTu8ss29lc=; b=ikWVV6X9U/A2dt/uLOydxPNDiYHYKiNLhHXB9r2WARiaq3iMmc8KuAQoGm9W6rVkWV tgy++R/MQT1G1Yc8RXnZ8FNPMBS3N0MUdY+Ej5L7U0iPhW0GJnaW0vpl4upoTeqrJ+a2 5j6NXxejm4hj3MUwiNRLxr7CEsM06BeRa9hLFVkMD1snA/e5UOEKgbzctsM7fjjXUdRc UsbMxRg9kqNRqoPqn6V1LfrUJYnw544PYqbkbXuXQrKN35r6TTQ5NX2JCxz6pzsuvqWC PnLARdjSngRxKY+ROxcIQrt8bVfQp4kbAX36ZNDem+SyaUMvK3j+1XVZpgjrP92VgOib 2drg==
X-Gm-Message-State: APjAAAUNRwWZo+x1aRi2zAvquj3opgzPE5h7DJSyGqJRDi1tAJGYIv4N eKKQXx4kaNtjy5ENSPzBqneIAg1mlkAsaRfgrE7H487/
X-Google-Smtp-Source: APXvYqzl/FISpdpaxIA8pQ5jpVbvKpOEtj95OJ9RYbtkbJ59EaCRLtDlecWy6TpVxuZDDI/nH60uWS1+OWtgl3M9/o0=
X-Received: by 2002:ac8:6ec4:: with SMTP id f4mr6488912qtv.271.1574309561511; Wed, 20 Nov 2019 20:12:41 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR10MB34184E50D2A25CA45EB84941E74E0@DM6PR10MB3418.namprd10.prod.outlook.com>
In-Reply-To: <DM6PR10MB34184E50D2A25CA45EB84941E74E0@DM6PR10MB3418.namprd10.prod.outlook.com>
From: Davey Song <songlinjian@gmail.com>
Date: Thu, 21 Nov 2019 12:12:30 +0800
Message-ID: <CAAObRXL+ydM=hAZUgXEJvocBk0GFPG6Fpa7xdog_Ns9Q1TL0Hg@mail.gmail.com>
To: Akbar Rahman <Akbar.Rahman@interdigital.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e34240597d3824e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/eigrlgymgBjgQDlT-dTUgCYhtMU>
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 04:12:44 -0000

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>
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
> https://www.ietf.org/mailman/listinfo/sfc
>

v2.23.0 | Report a Bug | By Email