Re: [sfc] Doubt about draft-ietf-sfc-nsh-12
"lizho.jin" <lizho.jin@gmail.com> Thu, 23 March 2017 15:52 UTC
Return-Path: <lizho.jin@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 D7AA1127078 for <sfc@ietfa.amsl.com>; Thu, 23 Mar 2017 08:52:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.275
X-Spam-Level:
X-Spam-Status: No, score=-1.275 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, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 pZ_5LKUD6bmH for <sfc@ietfa.amsl.com>; Thu, 23 Mar 2017 08:52:30 -0700 (PDT)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 71DF0126C23 for <sfc@ietf.org>; Thu, 23 Mar 2017 08:52:30 -0700 (PDT)
Received: by mail-pg0-x243.google.com with SMTP id g2so36901556pge.2 for <sfc@ietf.org>; Thu, 23 Mar 2017 08:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-transfer-encoding:content-disposition; bh=NuwvLcoZNRgVRkJaWQPKV428fR9tk0LLlFMmWfzxP3k=; b=aUZbBtvwbnFTCtggLsVOMHF4NiCARjHOUucoUu0Wr8VkKC8XfcfJ7HqgcxCJNiH2pU GIKlyS1DvYw6IXcn9iVt97Tb4feGkdK+WhZNt/UxVeQzqI4ljWdxIoiYS04/Ito0QReb PJOWH7vJc7nOfC3qNDTzlIW4DA68dKE0aTGrPgpbBNxZj0BPG4FStwOxEIBpYumRIFyA I25OtIyeTX3qjCQ3fe4SgXPWYy6XLGOq1wkAzQYeZdoWFmsHeYNFOCOWC83+F9L5Hon/ MiwR1kh30L4M/6q/WwnygLUmbSpuFHwsKv65cC4GXdadmz3o8HhXuj73q7PWtzR26hEM 8yOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-transfer-encoding :content-disposition; bh=NuwvLcoZNRgVRkJaWQPKV428fR9tk0LLlFMmWfzxP3k=; b=UXEWS/byikwnn/h1JhaLX0l2TSi4zfaRyP8gx2ksU1xb4+fegp6nWkmJdQoyEBfREi urMsMQETVhTWq5Ri6i417L5b4Jk+LdT+1L0NQttEQUM5kYri8IW3FrOPw8HPcs181tNA C+HlDpV8a6pjtvmcZk/IgH8e/EJEOcWMJLd3MmWkyqmi3v/m1q+1nfPFz53XCxC8SQsh IANrztOwhcVK3OmvFjJLthLMVdW8xLd59LszczkzW+uTnw9RjzFFe+muSZN4imj4d42L BaXizZxXRvrnaQ4QlPR0fl8uwWTOWLMJdCaT7TDnR2BhEw7SeFj0tjSQd0xSTY4AvKUZ 9fuw==
X-Gm-Message-State: AFeK/H3Btr3fUI4F1zzNQmKKUpwMnQ/sW1DhOXBcSe+6hVhiFMF80i3XdlwEvToerGgGyQ==
X-Received: by 10.84.232.67 with SMTP id f3mr3467977pln.42.1490284350095; Thu, 23 Mar 2017 08:52:30 -0700 (PDT)
Received: from LLIOK4RX6E0B076 ([103.251.128.66]) by smtp.gmail.com with ESMTPSA id n7sm11169604pfn.0.2017.03.23.08.52.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Mar 2017 08:52:29 -0700 (PDT)
Date: Thu, 23 Mar 2017 23:55:15 +0800
From: "lizho.jin" <lizho.jin@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: sfc <sfc@ietf.org>, paulq <paulq@cisco.com>, "uri.elzur" <uri.elzur@intel.com>
Message-ID: <905ED664-B5EC-434C-A823-99C68761E254@gmail.com>
In-Reply-To: <66bf1a04-d01a-e651-707f-f325edd9f0ef@joelhalpern.com>
References: <0C4ABB6D-6E5F-4C87-8EF0-F8D7FF8C95A9@gmail.com> <66bf1a04-d01a-e651-707f-f325edd9f0ef@joelhalpern.com>
X-Mailer: PC MailMaster/3.3.1.1013 (Windows 7)
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/YY3xsxBt0voi3BeTEBOBq60g-K4>
Subject: Re: [sfc] Doubt about draft-ietf-sfc-nsh-12
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
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, 23 Mar 2017 15:52:32 -0000
The content of the inner payload may change. Lots of service functions
change the content. NAT, HTTP annotators, ...
THe semantics of the inner protocol (TCP is still TCP,...) remain the
same. if the semantics are changing, then the service function
terminates one chain and starts another.
[Lizhong] then do you mean, a service chain is represented not only by the SPI, but also the Next protocol? There does exist some case to change the Next protocol after function process.
Yours,
Joel
On 3/23/17 11:15 AM, lizho.jin wrote:
> Hi Authors,
> I have a doubt with following description:
>
> Next Protocol: indicates the protocol type of the encapsulated data.
> NSH does not alter the inner payload, and the semantics on the inner
> protocol remain unchanged due to NSH service function chaining.
> Please see IANA Considerations section below.
>
> It says NSH does not alter the inner payload, but what if the SF is NAT,
>
> then the payload will be changed, right?
>
> Regards
>
> Lizhong
>
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>
- [sfc] Doubt about draft-ietf-sfc-nsh-12 lizho.jin
- Re: [sfc] Doubt about draft-ietf-sfc-nsh-12 Joel M. Halpern
- Re: [sfc] Doubt about draft-ietf-sfc-nsh-12 Kyle Larose
- Re: [sfc] Doubt about draft-ietf-sfc-nsh-12 lizho.jin
- Re: [sfc] Doubt about draft-ietf-sfc-nsh-12 Joel M. Halpern
- Re: [sfc] Doubt about draft-ietf-sfc-nsh-12 Lizhong Jin