Re: [Teas] [mpls] Comments on draft-ietf-mpls-rsvp-shared-labels

Matt Hartley <mhartley.ietf@gmail.com> Tue, 25 September 2018 14:16 UTC

Return-Path: <mhartley.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF9CD1312B8; Tue, 25 Sep 2018 07:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[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 Bvwhlx3MeDgr; Tue, 25 Sep 2018 07:16:40 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 190BD1312A8; Tue, 25 Sep 2018 07:16:35 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id b129-v6so11649529pga.13; Tue, 25 Sep 2018 07:16:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ommU9BIY0eth59lva7fWJlk4ejZxqke7CCSPQ3z7D8I=; b=ANTpQGblUDlwx4Z975EIH6mlLwU7i2W0hQ02mAbdcVSw4EIAe5V4LwqxxbEYhMN+sJ r8cg3zdgVysR/uo8YVIxGXWsZRiB90IREseayS6WkGsG/AmK2ok1e3xVunkmZw2A4n8i oTEKQtGqhSW5FtZcJBwYA00KkS4BcEFOqpTFAXQ8JOQnrMMX4NWu28JAA2cnLev9eb8/ e7JtbMpT8dEVNyc08kSAfrcVF/dbujHIQYiIqdo9Z+LsP/GpW0DbDXzKirJ0qzNdkbwW dFzvYZLEP/ZWuivEHa0XCHzZ/0oV8zhnL2/4eFtb9XZrqD02gZrKumwVer2/a/iwZCXf P0Aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ommU9BIY0eth59lva7fWJlk4ejZxqke7CCSPQ3z7D8I=; b=IK9UptOjYdqrYa4yJqmo2nQOoupHaC8Tz67/jZGVBaeSN9Qvc9f57X31k5pf0rHJxt 6L3pPBBlzvTTB5xHZO2A4XGj5xAcIRx0iRibLPjpbH1WXqhCM7N25VNXsnYDVtIRIvmK tbWSw3El+kcOhFJzt4L9N+N1AFHEgN0FMubCMjvmw3ajBlfqcj6+TdZc/TTcTJRdJ1Wy scGkGANIJygHdJDT1blSCrAVbe3ppg8kjZzPYXwauQZf08Osi/UbXzrOuIti2Xtxn0de cePDmxMOKjzXxB39ftgXq/I/5kT+SrRpbzYnNMZ1vmFTHAnklyZzCs0FGCL3rpdUTh00 BGfg==
X-Gm-Message-State: ABuFfojGfISuGc/+2EQvfP93QddwrGEYebtpZopKwaZp9JiIzfj0V0qo vG/jIFFUODG3HZnHHYQP4Yod36NbohgQNTOtx+g=
X-Google-Smtp-Source: ACcGV63tHGyP2+IMb2W1hKbqBryzIgrffhMti3yqAhS9FkV6df2ZaCStOhIos8owuITIOM+93qWymuL4zrzH6vM/2Tg=
X-Received: by 2002:a17:902:d915:: with SMTP id c21-v6mr1484116plz.134.1537884991532; Tue, 25 Sep 2018 07:16:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAKfnWBj5hWjGX0D5kuq6ya9p=0csB1C2h_-B6ZVhXpMm0=B6sw@mail.gmail.com> <CA+YzgTuESy7yaanHCfiDW74exHHVkpx8TY1t8m2ApggoEhUQgg@mail.gmail.com> <CAKfnWBgXfUaaY1QRRT1cuW=yx3LUeqaGThz9E76_tGVAnV1vug@mail.gmail.com> <CA+YzgTv8bVAMON442OqB5Rdi4B27cUvZZRfOeF9uLDV-oqHD=g@mail.gmail.com> <CAKfnWBh22BByZV-gzQ02T5=pFyQ1-ff1zAoiUbH-wWKJ1VFWEQ@mail.gmail.com> <CA+YzgTstGuaNHXTPwKvyC5_NeDoMkq4z-VXZWMGBuJW-mWErqQ@mail.gmail.com>
In-Reply-To: <CA+YzgTstGuaNHXTPwKvyC5_NeDoMkq4z-VXZWMGBuJW-mWErqQ@mail.gmail.com>
From: Matt Hartley <mhartley.ietf@gmail.com>
Date: Tue, 25 Sep 2018 10:16:19 -0400
Message-ID: <CAKfnWBjvN_9ccg+_Hrey+oHCz=RpREYUHtKHCpUXYhcpGxGBqw@mail.gmail.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: draft-ietf-mpls-rsvp-shared-labels@ietf.org, mpls@ietf.org, teas@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a0345d0576b2c01d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/TRS46hE_vqahQFi_FIrgDtYTBy8>
Subject: Re: [Teas] [mpls] Comments on draft-ietf-mpls-rsvp-shared-labels
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2018 14:16:42 -0000

OK. That works for me!

Cheers

Matt

On Mon, Sep 24, 2018 at 11:04 PM Vishnu Pavan Beeram <vishnupavan@gmail.com>
wrote:

> Matt, Hi!
>
> Great that we are in sync now. Please see inline for the response
> (prefixed VPB) on the last open comment.
>
> Regards,
> -Pavan
>
> On Mon, Sep 24, 2018 at 2:02 PM Matt Hartley <mhartley.ietf@gmail.com>
> wrote:
>
> Snipped..
>
>>
>> Can nodes other than the ingress introduce an ETLD into the Path message
>>>> if the ingress node doesn't? In particular, can an explicitly-allocated
>>>> delegation node do this?
>>>>
>>>
>>> [Pavan] No and No. ETLD is used only for automatic delegation.
>>>
>>
>> Do we need to say that explicitly? I don't think a transit node
>> introducing an ETLD would do much harm, but if you don't want/expect it to
>> happen then it might be worth putting that in just to close the loophole.
>>
>> [VPB] I don’t see the need for any additional text. We have explicit
> text in Section 9.7 stating that ETLD is used only if Automatic Delegation
> is requested in the LSP_ATTRIBUTES. LSP_ATTRIBUTES is included in the PATH
> message at the ingress.
>
>
>> Cheers
>>
>> Matt
>>
>