[mpls] Re: Request WG adoption for draft-jags-mpls-ps-mna-hdr-03.txt

Loa Andersson <loa.pi.nu@gmail.com> Thu, 27 June 2024 11:28 UTC

Return-Path: <loa.pi.nu@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 866A1C14F61D; Thu, 27 Jun 2024 04:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 7nicUcvpvlmB; Thu, 27 Jun 2024 04:28:26 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 D7EE3C14F6FB; Thu, 27 Jun 2024 04:28:25 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2ec52fbb50cso56587421fa.2; Thu, 27 Jun 2024 04:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719487703; x=1720092503; darn=ietf.org; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=4E7gwggrxCb+7AhUypayh2JOF5z7SmuTpOhkdpG3kL4=; b=kLD4pmwWuChLi5kOVuEJ+vfJ/9RRe7GVAOkjVOU4zwbjnpQVvKO8GucVbkP2/FVyfj s66pNizooKXmguwkoyCJPaIlAi9Zo7abTBy0+xrl4/5rVlx7cYlfWgtcfw+4nO0y3CVU l9kxyQFhkRoJoh/aMaA+I7kXvCZY02LiGH5t1diVzPc5ZfASqGWs4/ovjo6T1UBKEZVs Z5gWUlHDKUwUnDEpQrhA8Q/H55ZlI2BaYuWfP/wz7vIODd9XguInXAveqMN0nfrNG4jx wTrXZqf4p8sYJgSizYG2E+kw/UOyYHwqgpIj8iWApke3EPlMkb0AX+NK13l7TXe3s2ku vBCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719487703; x=1720092503; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=4E7gwggrxCb+7AhUypayh2JOF5z7SmuTpOhkdpG3kL4=; b=r2BSFvnbBaBvylRd+rfzsWOyTX+yjkYz5yinbzwaqvTj4f6MGFzylkQS4aZe5QFpcH dXEDf1AWlTGXFA1HKTqXsf5qR9kE3Qv1kAX/axQcHgcuvpy2U0GprO+I6iwJ4rhllQu5 UjyMUMtJVu9qYtL7O+o8yFEFsOsacsRIOB1Va0SGP+BypTj3v6jfy41dbg+ULBj6KwDm HXV+FN1F4sRor7TAZ57OB2yIyjktwXp++umxAL5LyG2geWmYwl+ajsxo5cOApxMwPm1h vQcvqTVWPqaGJojlem7myN3rf7fgNQ6DDukfTCvBLYw2Xb8Faic4XYtRI5aZxTSOty+1 +WKA==
X-Forwarded-Encrypted: i=1; AJvYcCVraw/mNPzXElJQrDM+sCKAcr8TUxvKdJb8x/OaPAjth2qnowsO1a4b33venrRgWcl8JbBrqL8tyRNNmSFGJyAP1EEC9kGGiDbzHFZPoGxqKWPu7UpO2T1OR3Nf8awiF9gKNA==
X-Gm-Message-State: AOJu0YyXdeGExdo21rQG4n9N5cT9k7F4Mv4z8SmBzjeUyATl71VJ3bIW q28J2DXpxX2pmHBhF4bNzJgiznyCMJ1hEp9BM82amY2wRWe5wLCluZPlXw==
X-Google-Smtp-Source: AGHT+IGYpsL4gWSFXgUT8J3Dt+b3KOwf1m/ZqdzseqJ+IW3tqiE2gePo84rlD/fti40fhkmBDHXBvQ==
X-Received: by 2002:a05:651c:210:b0:2ec:1708:4daf with SMTP id 38308e7fff4ca-2ec5b307bedmr75892951fa.47.1719487692905; Thu, 27 Jun 2024 04:28:12 -0700 (PDT)
Received: from smtpclient.apple (94.191.137.161.mobile.tre.se. [94.191.137.161]) by smtp.gmail.com with ESMTPSA id 38308e7fff4ca-2ee4a350d70sm2147041fa.45.2024.06.27.04.28.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Jun 2024 04:28:12 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-5C55D7E5-DAC6-433E-9B25-55333CEB0FE7"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Loa Andersson <loa.pi.nu@gmail.com>
In-Reply-To: <MN2PR11MB4064C712C5BC6320C5755442D0D72@MN2PR11MB4064.namprd11.prod.outlook.com>
Date: Thu, 27 Jun 2024 13:28:01 +0200
Message-Id: <69521B49-5B7A-4262-9409-7B332768F6C0@gmail.com>
References: <MN2PR11MB4064C712C5BC6320C5755442D0D72@MN2PR11MB4064.namprd11.prod.outlook.com>
To: "Jaganbabu Rajamanickam (jrajaman)" <jrajaman=40cisco.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (21F90)
Message-ID-Hash: 6VZTM673GJHO7NM6VPZD5V3KD7PAQUMM
X-Message-ID-Hash: 6VZTM673GJHO7NM6VPZD5V3KD7PAQUMM
X-MailFrom: loa.pi.nu@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mpls <mpls@ietf.org>, draft-jags-mpls-ps-mna-hdr@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: Request WG adoption for draft-jags-mpls-ps-mna-hdr-03.txt
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/vlQQDKZoblDgwaYPELL4oXR0ftM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

Jags,  

True, as long as the change is different per packet. 

/Loa

Sent from my iPhone

> On 27 Jun 2024, at 13:00, Jaganbabu Rajamanickam (jrajaman) <jrajaman=40cisco.com@dmarc.ietf.org> wrote:
> 
> 
> Hello Everyone,
>  
> Another important PSD use case that I can think of is the following.
> Apart from the number of bytes encoded in the ISD, in cases where intermediate nodes need to modify the AD, it is better to encode those ADs in the PSD rather than the ISD to protect against issues in classic ECMP hashing scenarios.
>  
>  
> Thanx,
> Jags
>  
> From: Loa Andersson <loa@pi.nu>
> Date: Thursday, June 27, 2024 at 6:11 AM
> To: Joel Halpern <jmh@joelhalpern.com>, mpls <mpls@ietf.org>, draft-jags-mpls-ps-mna-hdr@ietf.org <draft-jags-mpls-ps-mna-hdr@ietf.org>
> Subject: Re: [mpls] Re: Request WG adoption for draft-jags-mpls-ps-mna-hdr-03.txt
> 
> Joel, wg, wg-chairs,
> 
> No I don't think we are in the first case, ISD and PSD is not equally good
> for all cases.
> 
> - both Rakesh and I have demonstrated that PSD is much more straightforward
>    for direct export, and it is possible to align nicely with the base
> direct
>    export RFC. We don't miss bits here and there, we don't need to use
> two LSEs
>    for the sequence number optional filed, we don't need to map
> extension flags
>    from 8 bits to 6 bits. This is a case two situation. PSD would be better.
> 
> - it has earlier demonstrated that 19 octets worth of mutable data as ISD,
>    personally I believe that that is a too serious limit, since to my
> understanding
>    you for example you typically need at least 8 octets for a timestamp.
> This is
>    mutable data, so you can only put two timestamps in one packet. That
> seems to
>    me to be a limitation that we can't live with. This is a case 3
> situation.
>    ISD can't solve m ore than 2 timestamps, PSD can. I'm   not a an
> expert in the
>    area, so I leave it to the experts to tell me if I'm right or wrong.
> 
> - We also seen cases where adding "too much" ISD into the stack, gives
> us label
>    stacks that are too deep. If you want to put two timestamp in as ISD,
> you will
>    need to increase the label stack with 12 LSEs, which seem to
> excessive. A case
>    3 situation.
> 
> Yeah, so we need PSD. Please poll the draft-jags-mpls-ps-mna-hdr for
> working group
> adoption.
> 
> /Loa
> 
> 
> 
> Den 2024-06-26 kl. 21:35, skrev Joel Halpern:
> > Loa, you list three bullet points with three different results.
> > However, what has been shown so far seems to correspond to your first
> > case, which you state does not justify two solutions. Adopting a
> > post-stack data solution before we decide we are in case three, or in
> > case 2 and feel the tradeoff is right, seems premature.   It may well
> > be that the ps draft is the right starting point once we have agreed
> > on the problems to be solved. Which is why I am trying to understand
> > the motivations for Rakesh' iOAM dex draft.  (I do think we need to
> > support IOAM DEX.)
> >
> > Yours,
> >
> > Joel
> >
> > On 6/26/2024 3:30 PM, Loa Andersson wrote:
> >> Jags, authors, chairs, working group,
> >>
> >>
> >> I support making draft-jags-mpls-ps-mna-hdr a working group document.
> >>
> >> It has repeatedly been said by those who want ISD-solutions that
> >> PSD-solutions ar not needed.
> >>
> >> I think this is a fundamentally flawed way of asking the question.
> >>
> >> - if we have a choice between two solutions and they are equally good
> >>   for all cases, then it makes sense to try to find consensus for
> >> adopting
> >>   one of the solutions
> >> - if we have a choice between two solutions there both solutions "can
> >> do" all
> >>   cases, but there one is significantly better for one set of cases
> >> and the
> >>   other is significantly better for the remaining cases, we should
> >> cases we
> >>    should seriously consider going for two solutions.
> >> - if we we have the a choice between two solutions there one can
> >> solve part of
> >>   the cases and the other the remaining cases, the we need to go for two
> >>   solutions.
> >>
> >> /Loa
> >>
> >>
> >> Den 2024-06-26 kl. 04:50, skrev Jaganbabu Rajamanickam (jrajaman):
> >>>
> >>> Hello Chairs,
> >>>
> >>>    We would like to request WG adoption for draft-jags-mpls-ps-mna-hdr.
> >>>
> >>>    Updated the draft with the initial review comments and the latest
> >>> MNA header format.
> >>>
> >>>   Welcome your review comments and suggestions.
> >>>
> >>> Thanx,
> >>>
> >>> Jags
> >>>
> >>>
> >>> _______________________________________________
> >>> mpls mailing list -- mpls@ietf.org
> >>> To unsubscribe send an email to mpls-leave@ietf.org
> >>
> 
> --
> Loa Andersson
> Senior MPLS Expert
> Bronze Dragon Consulting
> loa@pi.nu
> loa.pi.nu.@gmail.com
> 
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org