IETF Logo Mail Archive

[lisp] Re: Routing Directorate Last Call Review for "LISP Distinguished Name Encoding" - draft-ietf-lisp-name-encoding-08

Dino Farinacci <farinacci@gmail.com> Tue, 16 July 2024 20:18 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C26C15152C; Tue, 16 Jul 2024 13:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, 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] 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 dvo19kBWRd62; Tue, 16 Jul 2024 13:18:09 -0700 (PDT)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 EA41AC151538; Tue, 16 Jul 2024 13:18:09 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id 5614622812f47-3d9c487b2b5so3412506b6e.3; Tue, 16 Jul 2024 13:18:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721161089; x=1721765889; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9MNxLci8/1qyGAlUAcbLxpeM4J/NWmXIryAw1SJPq70=; b=jRYg+pvV0b2OqDVP25ZvdIjRRv/Au094402m9dMS/eyOBRHOAPErxcWP4D9zv9beFR Z8p+TOkH4lpRTTxfRSmgfR5poW+0ML5G9C2GRVkHF/nq/FUAEPb0YCDzEcWGgrbHp/2E XD/zpDf85aPaFXnUA/W848ixy8s4vHyzYMQG10Eksa/up/5fCl10biCCEmeMWURYZ4Uu QNDfW5VIZjindR6JZEINa+vS63BEAoh1UQ6+avQcrxs4E3B1Xx76pFiE+vexjqvLdgU3 AGBqjfkfaTzWNMHu6oPa8uMKqpaqTU0UVX7BnZHxQTtmL8p6IER7kuozgIcqKbnaErqc xPXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721161089; x=1721765889; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9MNxLci8/1qyGAlUAcbLxpeM4J/NWmXIryAw1SJPq70=; b=vx2Y/kVQ/aUz4QRIiDJEt6YzoL9mU5BvIuC76bnZXH4RLYLPIqRVAabbHaN8aA8H3p 8fzrHsa1dHUPd55CaH8oGN3uOUIfolYIflR8OKo5QqE3Fqn8TeG/NlQBAHW1oaPMKyqM r4kupYhHw9hgeLRnyZ4H832RpxWzCQnB3rFWhGQqX6M+J8LFUMYwhfmjTZ2yvB/KLyI7 mDATNZY/tsa+n5Qs1tPRRr5haLZsRLEpbct8dw1IIyBgAAPFHTBe38Ql5boMtZ7rXLgb tWOeWgzjEg7+QM12jIThm/jDEDk16cnQe/oitNMxFYu2JnahuqEJ7FkqIJ/qRZPYf59q UPjA==
X-Forwarded-Encrypted: i=1; AJvYcCXzER4EWkM2aAQ+ulViDaKWmKgeiStC3bs/hHykFHtvdHfBIcvWlj0o3Z7bk/cK3jAdfd0Db8/kX9DOVkvWObu+qhnxgqERgIPsoM/R3PBtmr3KFGspH4WKWf5yzlMRh0UtWPY=
X-Gm-Message-State: AOJu0YwwjILi1vQQEJLG+st3Fp1WbQ2OeoYVzr6//OrCOEDyBMlXx4OK B4Ot4E0/omJIvCyifu0fXWsetB93v7+TSd+KGbV8O0AZL7zxXp/s
X-Google-Smtp-Source: AGHT+IFY2mY7tPCEjD1ULDnG5wWgV2+mEcd1VQvfbCjl2DWELCVCktgRnqj+7LYvbjI5AO0WyEByRg==
X-Received: by 2002:a05:6870:1816:b0:254:aada:cc8b with SMTP id 586e51a60fabf-260bd7789f1mr2631030fac.31.1721161089034; Tue, 16 Jul 2024 13:18:09 -0700 (PDT)
Received: from smtpclient.apple ([2605:59c8:30dd:9810:b405:edde:6df7:f0dd]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-78e39fdcbc7sm4348195a12.92.2024.07.16.13.18.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jul 2024 13:18:08 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <79C9ECAD-293C-48B8-B125-3BDA967592F6@gmail.com>
Date: Tue, 16 Jul 2024 13:17:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B98DA29-FE52-4697-9F50-B96C4F26C91E@gmail.com>
References: <60F5074B-1ABF-4188-BAAB-93674065EF06@gmail.com> <E705921B-A423-4B79-81B3-4CF31F012B51@gmail.com> <79C9ECAD-293C-48B8-B125-3BDA967592F6@gmail.com>
To: Acee Lindem <acee.ietf@gmail.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Message-ID-Hash: BYS4J2SZ2WGJZO7QSR373NWFEYYMOYBU
X-Message-ID-Hash: BYS4J2SZ2WGJZO7QSR373NWFEYYMOYBU
X-MailFrom: farinacci@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-lisp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-lisp-name-encoding@ietf.org, LISP mailing list list <lisp@ietf.org>, rtgwg-ads@ietf.org, Routing Directorate <rtg-dir@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [lisp] Re: Routing Directorate Last Call Review for "LISP Distinguished Name Encoding" - draft-ietf-lisp-name-encoding-08
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/QrS-bRXHpen5LXO4JzKw39dCgtY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Owner: <mailto:lisp-owner@ietf.org>
List-Post: <mailto:lisp@ietf.org>
List-Subscribe: <mailto:lisp-join@ietf.org>
List-Unsubscribe: <mailto:lisp-leave@ietf.org>

> This exposes my only high-level knowledge of the protocol itself. Maybe add a reference to [RFC9301] here as well.  

I will add.

>> 
>>> 2. In section 5, the final sentence fragment didn't parse and it
>>>   wasn't obvious to me how to edit it - "As well as identifying
>>>   the router name...".
>> 
>> Fixed. Thanks.
>> 
>>> 3. In section 9.2, The description of the onboarding process includes
>>>   very specific details that aren't fully explained. Would it be
>>>   possible to describe the use case at a higher level?
>> 
>> This is some text from the cisco guys. I don't know how to change that. They have the intellectual property on it.
> 
> That’s fine with me then. It was just unclear to me how a DN would provide stability to the reliable transport session - would this allow the session to be recovered using a different UDP for?

I don't know. I have copied Marc Portoles explicitly so he can comment.

Thanks,
Dino

v2.26.15 | Report a Bug | By Email | System Status