Re: [mpls] Proposed text changes to draft-ietf-mpls-sfc - proposed 4.1

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 08 May 2018 14:40 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C33B712E8DF for <mpls@ietfa.amsl.com>; Tue, 8 May 2018 07:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Y6KK-dmqPu_D for <mpls@ietfa.amsl.com>; Tue, 8 May 2018 07:40:33 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 1BFAC12EAA8 for <mpls@ietf.org>; Tue, 8 May 2018 07:40:20 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id w48EeIVV011191; Tue, 8 May 2018 15:40:18 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E8BCE2203D; Tue, 8 May 2018 15:40:17 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id DD64D2203B; Tue, 8 May 2018 15:40:17 +0100 (BST)
Received: from 950129200 (73.44.114.87.dyn.plus.net [87.114.44.73]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id w48EeGlL013306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 May 2018 15:40:17 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>
Cc: mpls@ietf.org
References: <00c601d3e6cd$8942b1d0$9bc81570$@olddog.co.uk> <7f5dded7-1489-53bc-64d3-a76ba3efd8ef@joelhalpern.com>
In-Reply-To: <7f5dded7-1489-53bc-64d3-a76ba3efd8ef@joelhalpern.com>
Date: Tue, 08 May 2018 15:40:14 +0100
Message-ID: <00e501d3e6da$7a789c20$6f69d460$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGT/UVEewDaGez1ZMarQ6dRizqOYgGRlzA8pJkqXKA=
Content-Language: en-gb
X-Originating-IP: 87.114.44.73
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-23832.000
X-TM-AS-Result: No--16.504-10.0-31-10
X-imss-scan-details: No--16.504-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23832.000
X-TMASE-Result: 10--16.504400-10.000000
X-TMASE-MatchedRID: 7ySqCuYCpfinykMun0J1wvHkpkyUphL9ktxvVMaWMbC1eX0jEQ9c6lHe 46ufce0d29PfXyjwtNf64hiArZWsep96I2eBiiaHA9lly13c/gF+Mk6ACsw4Jt9MUoGRBUKyHOW W/Rp/isrhfzyvfuuoteNlgvH35nu1TX7PJ/OU3vKDGx/OQ1GV8rHlqZYrZqdI+gtHj7OwNO2FR9 Hau8GO7hTsay5USVouqDiA87HoRqgx1RkbjH5+vHugkvaH3INcfHGj/y9OIKc=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/fBPguz0xaU4Kzc2UisPwpRO9s5s>
Subject: Re: [mpls] Proposed text changes to draft-ietf-mpls-sfc - proposed 4.1
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 14:40:36 -0000

Thanks Joel,

Yes, that is a good refinement.

A
> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: 08 May 2018 14:14
> To: adrian@olddog.co.uk; mpls@ietf.org
> Subject: Re: [mpls] Proposed text changes to draft-ietf-mpls-sfc - proposed 4.1
> 
> The opening sentence you have proposed for section 4.1 is technically
> accurate, but seems misleading.  One of the benefits of NSH is that it
> has a path identifier that SFF do not change, while using an explicit
> position indicator.  I suggest a small text change below.
> 
> Thank you,
> Joel
> 
> On 5/8/18 9:07 AM, Adrian Farrel wrote:
> ...
> >
> > 4.1.  Label Swapping for Logical NSH
> >
> >     The primary use case for SFC is described in [RFC7665] and delivered
> >     using the NSH which, as described in [RFC8300], uses an encapsulation
> >     that is modified at each SFC hop along the chain to indicate the next
> >     hop.
> 
> s/that is modified at each SFC hop/with a position indicator that is
> modified at each SFC hod/
> 
> ...