Re: [mpls] Another way...

Jaganbabu Rajamanickam <jaganbaburietf@gmail.com> Thu, 21 March 2024 03:10 UTC

Return-Path: <jaganbaburietf@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 1A1FEC14F70D for <mpls@ietfa.amsl.com>; Wed, 20 Mar 2024 20:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zG3h45btqnch for <mpls@ietfa.amsl.com>; Wed, 20 Mar 2024 20:10:05 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67DB2C14F708 for <mpls@ietf.org>; Wed, 20 Mar 2024 20:10:05 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-413f4cb646dso3745675e9.1 for <mpls@ietf.org>; Wed, 20 Mar 2024 20:10:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710990603; x=1711595403; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iDxvk5YE6Z1QOgtWcQbbvQJXoeqQQfMWs/UnyVxbaY8=; b=llPkVOKsWpSGW9cCBYE8UkUOTniAYrs4rbPvoA/bkwdCXdaea7KmXyjGyQVSj1IoCu T7g8yFk5FUE+UMtvXCsf+BZaFeObBR1I2DWMS/vDCtjZO8Y982fo17e6sidQ4DTaAPDW nhkTx3/x5waDE5A3RJ4kxCo+NG0bQPqxK/YNyST2InCDsL2jl6f8mclwWNss2Z7b/zVN yRmjHntm0YT8beMOu6A0whu+uvJVZ0IXVlC9zC6TQgm7vGCS7qI9r7rr11jkxkWbnTXL 2dKpwsT8guJhE5Y8a82YPu8Hx6+hx9QPeE4e/OSTqOMtsSW1RgL+yKXb+zD77T+NC0s0 hJLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710990603; x=1711595403; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iDxvk5YE6Z1QOgtWcQbbvQJXoeqQQfMWs/UnyVxbaY8=; b=T7dhFI6qRJfQcyVjIV8EIZdMVb7O4lfREAzfDfJIxmnf5Ti7CsS7l36h6fgOVg0UdZ XuoJ/9UvzutdNsoKFNmq5vXdleZA1RB9Oii38VOT6Y0jKiV3A7im9XU1A0j4yWXClhDE yueG10APS/sgMaRWsx6aWGSBz6SgINe6DqROtGdgA+Y1TP1iySRsWmxESeEeXhFv7xfL nP5owXrcHo0js/gnkOXVwzCH71/3QmeXGsL4txkIU8wx3VM2FMZGKfPKFbSUx83OGYQT qNRpl9R9pYQIV2/7Q9ZPyvjzRLvElt93Zu4PMADg77sj5KlFYcVRe9JyJCHmq7gUuvvd 0z+w==
X-Forwarded-Encrypted: i=1; AJvYcCUZK3yuTNvwCOCGubg5LJZ8YZR50wIYG7LAiC0QLb3FUBEfLs1keQJ6hXVtDo+D7hLJFml5yZNXznzrz+vE
X-Gm-Message-State: AOJu0YyCHZiGfsE9zY7Y2srMdYqkiIW2olaqrK1cquhWff1N9CgkrqaQ F92NfZXYcI460KL0dSd285p4DQEIGb7BAtjjlGEd23ZH6Ow4bCJxT+AsbAROWpsXAg85Zlmfgf0 q4x2Laj2YbtJvocLkaReNUuynMckzesqjysTeIw==
X-Google-Smtp-Source: AGHT+IHX2MW3t9tiYpLnM6CyPGiy3nHdiJSlzMqnrXKVsVgJSPlzIBLuDSYH9/L654Rv4tbL2MAmh2B8yBq0l9f0/jA=
X-Received: by 2002:a05:600c:35c1:b0:414:860:bdc9 with SMTP id r1-20020a05600c35c100b004140860bdc9mr393677wmq.33.1710990602631; Wed, 20 Mar 2024 20:10:02 -0700 (PDT)
MIME-Version: 1.0
References: <EC290C02-4B81-4ABF-B1D8-A36849C104AC@tony.li> <BY3PR13MB4787EBC452CB744B3EEFCC799A2A2@BY3PR13MB4787.namprd13.prod.outlook.com> <11840BF7-650C-4665-9E8D-8173F1451856@tony.li> <8e38ed70e0429b891cd89261e4221df9.squirrel@pi.nu> <CAPOsKjHcc5xrGRL-MEMW2TcYgrVXwO9o0MdekBwMTxC2zcvEHw@mail.gmail.com> <8c402657e45649528762f470d37237b6@huawei.com>
In-Reply-To: <8c402657e45649528762f470d37237b6@huawei.com>
From: Jaganbabu Rajamanickam <jaganbaburietf@gmail.com>
Date: Wed, 20 Mar 2024 23:09:50 -0400
Message-ID: <CAPOsKjH1cdgkjGDnO+L-MVbMem+D_3mWToDfQLtt=411n8sq+A@mail.gmail.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: "loa@pi.nu" <loa@pi.nu>, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001583540614230bdb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/4Zt6s1jEaejoO3bYAGu39otEyV4>
Subject: Re: [mpls] Another way...
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 21 Mar 2024 03:10:10 -0000

Hello Jie,

   I was mentioning an option of using the PSD offset opcode as an
indicator for the PSD presence.

   In case PSD offset opcode is encoded in the Format-B, then it is in the
same level as proposed "P" bit, so I did not see any reason why this
approach always consumes additional LSE.
   I agree that if anyone wishes to encode an ISD opcode using Format-B
along with a PSD, it may require an additional LSE beyond what the current
approach entails


Thanx,
Jags

On Wed, Mar 20, 2024 at 8:24 PM Dongjie (Jimmy) <jie.dong@huawei.com> wrote:

> Hi Jags,
>
>
>
> Thanks for sharing opinion on this.
>
>
>
> In my understanding the PSD offset opcode is optional and is not needed
> when PSD follows immediately after the EOS.  Making it mandatory for PSD
> would always consume one LSE and would reduce the space available for ISD.
>
>
>
> Another point is the position of the PSD offset opcode in NAS is not
> fixed, which means for a node which only supports PSD, it may need to parse
> the preceding ISDs to find the indicator of PSD. This is not efficient in
> implementation, and also makes the implementation of PSD coupled with ISD.
>
>
>
> Best regards,
>
> Jie
>
>
>
> *From:* mpls <mpls-bounces@ietf.org> *On Behalf Of *Jaganbabu Rajamanickam
> *Sent:* Wednesday, March 20, 2024 8:44 AM
> *To:* loa@pi.nu
> *Cc:* mpls <mpls@ietf.org>
> *Subject:* Re: [mpls] Another way...
>
>
>
> Hello All,
>
>
>
>     In the PSD case, we may need a new ISD opcode to indicate the offset
> of the start of PSD if PSD is not encoded immediately after the EOS.
>
>     In section 6.1 of our PSD draft (
> https://datatracker.ietf.org/doc/draft-jags-mpls-ps-mna-hdr/ ). We
> already have mentioned that the new ISD opcode will be allocated with the
> format option of Format-B or Format-C.
>
>
>
>     I think we could use the same opcode to indicate the presence of PSD
> as well. The offset could be zero or Non-Zero value.
>
>
>
>     If we use a reserved bit in the Format-B to indicate the presence of
> PSD and in case we encode the new PSD offset, then still we need to add an
> additional opcode to be encoded.
>
>
>
> Thanx,
>
> Jags
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Mar 14, 2024 at 12:58 AM <loa@pi.nu> wrote:
>
> All,
>
> I have been thinking about using an OpCOde for a while, but have been
> reluctant to propose it. Several reasons, but mainly as the encoding grows
> more complicated we would either need a general encoding document or
> include this in the framework. Until we make up our minds there is some
> time and that delays progress of the other drafts.
>
> Another reason is that sometimes it is an entire LSE, and sometimes it
> is not.
>
> If we have just one OpCode after the Format A LSE (Opcode P (for PSD) it
> is no big deal.
>
> Example:
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      MNA-Label=bSPL (TBA)             | TC  |S|    TTL        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Opcode P  |        Data             |R|IHS|S| Res |U| NASL=0|
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> and
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      MNA-Label=bSPL (TBA)             | TC  |S|    TTL        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Opcode X  |        Data             |p|IHS|S| Res |U| NASL=0|
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Is roughly equivalent :) (I said roughly).
>
> However if there is another OpCOde
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      MNA-Label=bSPL (TBA)             | TC  |S|    TTL        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Opcode X  |        Data             |R|IHS|S| Res |U| NASL=1|
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Opcode P  |       Ancillary Data          |0|  AD   | NAL=0 |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Is less efficient than
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      MNA-Label=bSPL (TBA)             | TC  |S|    TTL        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Opcode X  |        Data             |p|IHS|S| Res |U| NASL=0|
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>
> Note: The discussion we have now about "changing" the format would
> potentially affect the Framework. Or even motivate a general MNA
> encoding document.
>
> Since both the OpCode and the p-bit are ISD, I think they should be
> assigned in draft-ietf-mpls-mna-hdr.
>
>
> /Loa
>
> >
> > In fact, it’s not a whole label.  If we’re talking about PSD, it’s
> > very likely that there’s nothing in ISD except for the PSD indication
> > and this opcode would fit in the Format B LSE without any additional
> > overhead.
> >
> > One could, in principle, generalize this to make the entire Format B data
> > space into extension bits of various flavors, with PSD being only one.
> >
> > We have many extension mechanisms, not just reserved bits.
> >
> > T
> >
> >> On Mar 13, 2024, at 11:36 AM, Haoyu Song <haoyu.song@futurewei.com>
> >> wrote:
> >>
> >> I think this is very inefficient. While only a single bit is sufficient
> >> to server the purpose, why dedicate a whole label?
> >>
> >> Haoyu
> >>
> >> -----Original Message-----
> >> From: mpls <mpls-bounces@ietf.org> On Behalf Of Tony Li
> >> Sent: Wednesday, March 13, 2024 8:29 AM
> >> To: Loa Andersson <loa@pi.nu>
> >> Cc: mpls <mpls@ietf.org>
> >> Subject: [mpls] Another way...
> >>
> >>
> >> [WG chair hat: off]
> >>
> >> Hi Loa,
> >>
> >> It occurred to me that another way of indicating the presence of PSD
> >> would be to allocate an opcode to serve this purpose.
> >>
> >> This requires no reserved bits and no pre-definition of any value so it
> >> intrinsically cannot disappear.
> >>
> >> Tony
> >>
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >
> >
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>