IETF Logo Mail Archive

[sfc] Doubt about draft-ietf-sfc-nsh-12

"lizho.jin" <lizho.jin@gmail.com> Thu, 23 March 2017 15:12 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 48AD71296F2 for <sfc@ietfa.amsl.com>; Thu, 23 Mar 2017 08:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.276
X-Spam-Level:
X-Spam-Status: No, score=-1.276 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] 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 JzlqvzZAKRzo for <sfc@ietfa.amsl.com>; Thu, 23 Mar 2017 08:12:40 -0700 (PDT)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (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 ED51F129490 for <sfc@ietf.org>; Thu, 23 Mar 2017 08:12:39 -0700 (PDT)
Received: by mail-pg0-x241.google.com with SMTP id 81so28699858pgh.3 for <sfc@ietf.org>; Thu, 23 Mar 2017 08:12:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:subject:mime-version :content-transfer-encoding:content-disposition; bh=6tnR3u//Y57kmrNyogFjNJ8uiU4IVxUSXCRidpazMZk=; b=Ts5efWhVgL9YwI2BZXjwfyxtJO/iYZMyo1iG95xonqtNbNtZHg/91Hre28r3w57o1R 4SvaHcmmlsQ5jBKnRzKGFnQaAODE/YdM5OzuICghxK+FKb6N6rjK9uPX6FrdOhPthYUS 9dbHe5w7q9KmKkCr8APzcU+be7E13zoz/W0S/UTaCdN/PYSKqIT+dGrokztYApAwrVYs aXud/LOEFIJmAE/mOONA7u8C3ekD4kdh8ic+oPZxdqNK1WfuvJTE9TxMvxJqRwj9ibmg jgvN0/7jN6lTdkjs1Tb+oyISEyJ29EEvXTbryJwHtFJZL8Y9M7BSemKiZUqsdoPyGQJT ONwg==
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:message-id:subject:mime-version :content-transfer-encoding:content-disposition; bh=6tnR3u//Y57kmrNyogFjNJ8uiU4IVxUSXCRidpazMZk=; b=O03q8sl+5bni6np770Bf4nLfKpp5Ji4X4L4yv3unv3Z+BambD6cH1PiBbxAIsHyrtK qXiO606FlZvr915wj0Nr3CNq6pmpujBR18v1PBIi2w1IniQygrhKQp6p2hy//h/8b+9o yMbt5/lFunOR/96RUgVjleAFhT86kJUooeI5DYhTX9QnYADornIyFC5UZONhiqurqdu1 f279zqCCOBv5tXjcGSmdJ2ePE3NIyr5eE3DhkmvUwGBi6OPF8/fRFsO12jQYJKVHHIjz 91hXj9sd9yQK3xbBLWF1UzFeVaNefm0VmP2O/Sm6RpyQJt6nY5w8T1KuQDK4CXcQqSnf ifHQ==
X-Gm-Message-State: AFeK/H3PhHs8O3HrwVMZT7lBqpgp5vgRTbtbOcUKqx6BjY1W834KXHDoiEBL+Sn0Lha2YA==
X-Received: by 10.99.144.65 with SMTP id a62mr3461799pge.151.1490281959347; Thu, 23 Mar 2017 08:12:39 -0700 (PDT)
Received: from LLIOK4RX6E0B076 ([103.251.128.66]) by smtp.gmail.com with ESMTPSA id l71sm11070468pga.7.2017.03.23.08.12.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Mar 2017 08:12:38 -0700 (PDT)
Date: Thu, 23 Mar 2017 23:15:16 +0800
From: "lizho.jin" <lizho.jin@gmail.com>
To: sfc <sfc@ietf.org>, paulq <paulq@cisco.com>, "uri.elzur" <uri.elzur@intel.com>
Message-ID: <0C4ABB6D-6E5F-4C87-8EF0-F8D7FF8C95A9@gmail.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/c_OsMP8GksJsnPZ7ToF4v8HQCg8>
Subject: [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:12:41 -0000

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

v2.23.0 | Report a Bug | By Email