Re: [mpls] Request for comments on draft-malis-mpls-sfc-encapsulation-00.txt

"Andrew G. Malis" <agmalis@gmail.com> Sun, 24 June 2018 16:29 UTC

Return-Path: <agmalis@gmail.com>
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 3FC39130E12; Sun, 24 Jun 2018 09:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_PASS=-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 ra_IWVGju3Ry; Sun, 24 Jun 2018 09:29:48 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 BC998130DDA; Sun, 24 Jun 2018 09:29:48 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id l22-v6so10318365oib.4; Sun, 24 Jun 2018 09:29:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xZ8AneNcJVbWE0HVhEPLV+pVuIz9gbvlZoFT9iDi+NY=; b=L8gjAGTTACNUs2HRktHxozTt184pja/ADOOsupKNil/0DT4VtOIuzmNqTiIqySh8wj 8stBcGth2UWwExT0JXiZ/Zfd1YsUGSnM6R0155q78CVbisDL+fv6V/Fn5zhys8K0j1dq ISRj3KmC8SrY6TvsnzcyeNR++m1UGnXJ51CMzqn13unFRwxX8MUeAZHPe4mMSzI4jaSj cmHKRbCQ+ayBrbjqhHCnEjWaj0Jsg+aGB5zETtAf3jAweVN7vWUDx25uGMLm8EJ1WGTt k9IovbS5nAQb1UXd+hyMMrwxIG/+uqKVvbmJiUUWfv1GYPeQCBDPEXZS2INEWHgG1drc YLgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xZ8AneNcJVbWE0HVhEPLV+pVuIz9gbvlZoFT9iDi+NY=; b=KysNsvk9GEb6RwFn7i4Uht9vNFCzLWGx5DQpxN31Wpj+YFFSbajvcoQAV8b7Cfw1u2 XVZiZejui3iuVczeKeR75m/XOJM5E2Li0AIrTTHLmKkcSWt8dtBPSCMdq68fL8YnTXVS md4qXIXJ0sN2eetyN6qv4s39yCtH7sYGDbUnuoV6N7qxq0UyWQ+9DWRIhcmtqn8bFm0f 26v/u9wOiSzTaWDHGzQWDVQ8uIs9urxrvbBI7TQcsfFwgbK1Z08+FOjMdurcPPq2i+56 otHSk5kagOTwdx4YGPY11wmQlmQb9QrHXxzgoqmhXaxF6zPBjHvjCXTbUU62GCusjxJ2 dE2g==
X-Gm-Message-State: APt69E2vc2OcDYqSMxnW3wsjv3egFrdzVZf0Z5vMjezdGnHzL9kyAmkh 4oF2iDMcP8EWYLBTWf4/ytIuKAL3bXsvjmlFY1w=
X-Google-Smtp-Source: ADUXVKJF//atuEC8Wr+ul+XLUqEnRLHW03CcY5s27zTkUnOvRAjxbVp47nBXNfUPiSxGy1UumQLW2ujpo2ZYT2D4C3A=
X-Received: by 2002:aca:e6c2:: with SMTP id d185-v6mr4771503oih.154.1529857788046; Sun, 24 Jun 2018 09:29:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:30c3:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 09:29:27 -0700 (PDT)
In-Reply-To: <DB5PR0301MB1909733B4E15C94FED93B9D89D4B0@DB5PR0301MB1909.eurprd03.prod.outlook.com>
References: <CAA=duU1jh5vw37U+st3oNgR7bLmod__Qub8A4x2LEXmP-rwppA@mail.gmail.com> <DB5PR0301MB1909733B4E15C94FED93B9D89D4B0@DB5PR0301MB1909.eurprd03.prod.outlook.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 24 Jun 2018 12:29:27 -0400
Message-ID: <CAA=duU3URO7GTT7Ricwk7YjziabkSfyg3LDaWbXm-sxA1+3NOQ@mail.gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000372a0056f65c62d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/p8WkvZ-Gxg_GHC57Enmv_tLtFBA>
Subject: Re: [mpls] Request for comments on draft-malis-mpls-sfc-encapsulation-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.26
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: Sun, 24 Jun 2018 16:29:52 -0000

Sasha,

Yes, thanks for asking, we can add that to the next revision. The intent is
that the NSH label operates similar to a PW or VPN label, so whatever
applies to them should apply to the NSH label as well.

And thanks for reading the draft!

Cheers,
Andy


On Sun, Jun 24, 2018 at 11:29 AM, Alexander Vainshtein <
Alexander.Vainshtein@ecitele.com> wrote:

> Andy and all,
>
> I’ve read the draft and I have a question regarding position of the SFF
> label in the label stack.
>
> The draft states the SFF label is located at the bottom of the stack and
> immediately followed by the NSH header.
>
>
>
> I wonder if it is possible to have some special purpose labels to follow
> the SFF label. The relevant example could be GAL (RFC 5586) followed by the
> GACH for OAM purposes.
>
> RFC 7708 has allowed this for PW labels which originally also have been
> defined as BoS only
>
>
>
> Regards, and lots of thanks in advance,
>
> Sasha
>
>
>
> Office: +972-39266302
>
> Cell:      +972-549266302
>
> Email:   Alexander.Vainshtein@ecitele.com
>
>
>
> *From:* mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of *Andrew G. Malis
> *Sent:* Tuesday, June 19, 2018 6:14 PM
> *To:* mpls@ietf.org; sfc@ietf.org
> *Subject:* [mpls] Request for comments on draft-malis-mpls-sfc-
> encapsulation-00.txt
>
>
>
> I’ve just uploaded https://tools.ietf.org/html/draft-malis-mpls-sfc-
> encapsulation-00 . It’s a short draft that discusses how to carry SFC
> packets that include the NSH over MPLS from one SFF to the next, so that
> SFFs that support the NSH can be connected via MPLS. It also includes the
> ability for MPLS nodes to support more than one SFF. Comments are
> appreciated!
>
>
>
> Thanks,
>
> Andy
>
>
>
> ____________________________________________________________
> _______________
>
> This e-mail message is intended for the recipient only and contains
> information which is
> CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have
> received this
> transmission in error, please inform us by e-mail, phone or fax, and then
> delete the original
> and all copies thereof.
> ____________________________________________________________
> _______________
>