Re: [mpls] Notes on draft-jags-mpls-mna-hdr-04

Greg Mirsky <gregimirsky@gmail.com> Sat, 07 January 2023 01:20 UTC

Return-Path: <gregimirsky@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 D0D37C15152C for <mpls@ietfa.amsl.com>; Fri, 6 Jan 2023 17:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RV1PAJBpSu9l for <mpls@ietfa.amsl.com>; Fri, 6 Jan 2023 17:20:57 -0800 (PST)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (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 507D2C14F606 for <mpls@ietf.org>; Fri, 6 Jan 2023 17:20:57 -0800 (PST)
Received: by mail-qv1-xf34.google.com with SMTP id o17so2182711qvn.4 for <mpls@ietf.org>; Fri, 06 Jan 2023 17:20:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=T0qsubXDZ+kqCShVC9kCNBQQVXMyy/GwXq7VPo+kcqY=; b=KMOBYduYvvvr42FR3lCotsAsZ9ZBIZdq25UKrdsBap2AYmBh2Y8lSfamtUDmCfdY7o TM+uyJBuWjs7U/jgA9Adxjsr7DwvC9quInOfFqebC9gfeXfraAI0Q4mwfBfI9LouReTl 3rPXQ9axWD5wcDuQVY6e3GrwnLfIFXchw3Pv/TrK6bH+lr6n5KcqJnm938ZKB0Dho59A jPXxPTmEU8oTVnuVBcue2o34pn9oHogfg3TSAjid37/zsawB79713zG4x18sBRxHJUm9 +l6OI4oRbyFD5QBruYleehilplfPurH1BctJET+RI5NhtkM6Yu3kvNREMBPNQXDP3KpK t+Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=T0qsubXDZ+kqCShVC9kCNBQQVXMyy/GwXq7VPo+kcqY=; b=wK+5G3h+R7WZkJvOzFX+9BCAoVgkmV2EHSX5TD9u/BEFxcsURPT5z4F1RZzJsUGrTD gdmYPr4LB57wYxk3mQ70kz73x9ejP8C9KNIPxGlYvQfugss7k0fuAHiDeggOYpf3vOjC qN3a46DS/IcK0s/lMmbUs3MoSmOHoF4KxiNU3cVwYGdz9m9odqJuhxiwO2zXp3uytKHM 3cjCzO6zGeaFRPZ3viUBx00xnTpvrGb5HI6phvZf5SpyLQvlak6LLpvwqejOmgwbmda0 V8wkfO0IuxnlG4C5jIjVnFGvEV76HNcdmSbtKV5GK3og++PMVO/y2NRe2XWg/+SJnuhS nd8Q==
X-Gm-Message-State: AFqh2kqy9HumrK5QL9oAXsq6QzCB2Iy3Ag7CifxEVFy1pTNSCWzpHm60 +ggeM7iYIGSfOWv/bvX/lqwDKeawWsgDWVleKbIdioET
X-Google-Smtp-Source: AMrXdXvjAwJbgunHKBqX3SewOK70x+jiae/VdXkwBa0gBZD0WZz2o5fabJ/gK5xJlVCWiwy5IjOi5wBtRprp6HzPDA8=
X-Received: by 2002:a05:6214:3992:b0:532:1398:9247 with SMTP id ny18-20020a056214399200b0053213989247mr405833qvb.51.1673054456171; Fri, 06 Jan 2023 17:20:56 -0800 (PST)
MIME-Version: 1.0
References: <CA+RyBmX14e=5P6jxpxCm1LYVJZet2bn-OjzXkTSAJ9VGDAZoBw@mail.gmail.com> <CA+RyBmUMp6Zxit=_qnrOCjMAG0uQ5XNwE7A2vCBoZUnviqfZ_w@mail.gmail.com> <BY3PR05MB8081FC71A7FD563B4300200CC7FA9@BY3PR05MB8081.namprd05.prod.outlook.com> <CA+RyBmWcq+F-efXrBQgX8eRrfW=ywFRuVDSqYqjyAK9teHfx+g@mail.gmail.com> <2D4CB479-19DD-4514-8C02-E5896FA8D084@tony.li>
In-Reply-To: <2D4CB479-19DD-4514-8C02-E5896FA8D084@tony.li>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 06 Jan 2023 17:20:45 -0800
Message-ID: <CA+RyBmXg7jhXM6fgXag2yZwa+vkhGL-WoLze-cyYBLpC__CfiA@mail.gmail.com>
To: Tony Li <tony.li@tony.li>
Cc: John E Drake <jdrake@juniper.net>, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008cd34f05f1a25878"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/MaoT6_1Q5_Lbq-HnsLhkZBzQheA>
Subject: Re: [mpls] Notes on draft-jags-mpls-mna-hdr-04
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: Sat, 07 Jan 2023 01:20:57 -0000

Hi Tony,
to confirm that your explanation of the scope of the Unrecognized flag
helped me.

Regards,
Greg

On Thu, Jan 5, 2023 at 12:36 PM Tony Li <tony.li@tony.li> wrote:

>
> Hi Greg,
>
>     0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                 Label                 | TC  |S|      TTL      |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Opcode    |        Data             |P|IHS|S|Res|U|O|  NASL |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    | Opcode = 3  |              NAI              |S|  Data |  NAL  |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    ~1|            Ancillary   Data               |S|Ancillary Data ~
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |1|            Ancillary   Data               |S|Ancillary Data |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>    - None, one or more Format C LSEs with Opcode 3 MAY be present in the same NAS.
>    - Each Format C LSE with the Opcode 3 MUST be followed by one or more Format D LSEs carrying associated Ancillary Data.
>
>
>
> That’s correct.
>
>
> If my understaning is correct, I have some questions about the Ancillary Data encoding:
>
>    - Can an AD associated with the particular NAI span more than a single Format D LSE?
>
>
>
> Yes, certainly.  AD length is only bounded by the NAL plus other actions
> within the same LSE.
>
>
>
>    - Can a single Format D LSE carry ADs of more than one NAI?
>
>
>
> Good question.  We have required an action to specify the amount of AD
> that it needs, but we have not specified any kind of granularity. This
> could reasonably be in bits, octets, or LSEs. If it’s in bits or octets, we
> might need to talk about data alignment.  If it’s in LSEs, we will need to
> talk about efficiency.
>
>
> And I still need a help to answer How a node skips an AD associated with the unsupported NAI?
>
>
>
> I think I addressed this in my previous reply.  Please let me know if that
> was unclear.
>
> Regards,
> Tony
>
>