Re: [pim] Benjamin Kaduk's Discuss on draft-ietf-pim-msdp-yang-15: (with DISCUSS and COMMENT)

Alvaro Retana <> Mon, 02 March 2020 15:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DB7983A0922; Mon, 2 Mar 2020 07:35:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dlqvgVhwC_e7; Mon, 2 Mar 2020 07:35:10 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6E7C73A0926; Mon, 2 Mar 2020 07:35:10 -0800 (PST)
Received: by with SMTP id t7so271103edr.4; Mon, 02 Mar 2020 07:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=6SfrgbYV0XIeGb9EnUppAJ5anPRq7zMRtcjyFBKyito=; b=gCfT2Kw3Fc2co2uhFn6JHsefNO9GgMpX3f2qBn0ClnzfIm6rakAEJVPSMzORRDSMTO bwy+ayhKhMdTpQcWu01lAqxvfBfzdkJaSpMPbpoV2P9WBw3rJgsyByNBBPzvpSPzxsTR dKk4yqWoinpDIz3HMWjlHxqGFqex59xjHREs8heerci1eNdB6CboTZFFlmOZT7Zl3LnS wgHY8AMBJA/RNad/97h59nAXpYVJGZrVNi0Da5E9JWldlLJZDmAq9kpVrzJuG0KbBPQ9 5+Z4c87otAY3l1oX+W+FuKKg4FEa+dzygZFxxYiOfUhQWvsn7BOfmzXpPe25brK9cOA2 fPHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=6SfrgbYV0XIeGb9EnUppAJ5anPRq7zMRtcjyFBKyito=; b=EeMWdVDMrJtyQJxc43WoTS9M7QmYS4OdLDgeUBXSfQj81CnHBmbL4wiQBi0i0vHVEM Zls9d6sYvPafO2TovMwYYXSKBCRqgmjfu+BcOKMa5bNyqSo4+IxXGf6YNW7NDK1RFzmK rIHik1ITsQk/LCo6RVKVFQX3pheOLEETq/4MeFxiTXUpGQjHkq9KU0cNkJgGXSTPojIn 055o1MxD6SoGB9NBbpJsHStKZrKSuSv+9Bd2H7dPPKLFintsOOSIYNloWVcktj2/AX7K 0AAVrfgZEQdkQ0bgEeGYn8mQDNGhOqXG7BJjGr80YgHuVWOOe2tqeO+2ODo7F8Mv4YmU TuIQ==
X-Gm-Message-State: APjAAAXwe7zc8u4NRw/KwsG8Tg8Jvb1fku253uvsgWh+rBZoqZea766a HN0p1JHS0ZMWJXJvb2j9X/MHhHol9dl7g6T/nYtgNgYH
X-Google-Smtp-Source: APXvYqyn48HdqNw3zqp+eN2LnlPir8WMY9PVsEQ3dBfYdzuXHxrh19h9xo6ZuqU99kzQkKA894rgMj02BO39Oh8PzNM=
X-Received: by 2002:aa7:c71a:: with SMTP id i26mr17632128edq.300.1583163308868; Mon, 02 Mar 2020 07:35:08 -0800 (PST)
Received: from 1058052472880 named unknown by with HTTPREST; Mon, 2 Mar 2020 15:35:08 +0000
From: Alvaro Retana <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Date: Mon, 02 Mar 2020 15:35:08 +0000
Message-ID: <>
To: Benjamin Kaduk <>, The IESG <>, Benjamin Kaduk via Datatracker <>
Cc:,, Stig Venaas <>,
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [pim] Benjamin Kaduk's Discuss on draft-ietf-pim-msdp-yang-15: (with DISCUSS and COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Mar 2020 15:35:12 -0000

On February 28, 2020 at 7:05:28 PM, Benjamin Kaduk wrote:



Thanks for your review!

Just replying to a couple of points.  I'll let the authors take care
of the rest of the replies and the updates.

> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> I don't think there's enough clarity on what authentication schemes are
> supported and how the YANG configuration interacts with MSDP operation.
> If I'm reading^Wsearching through RFC 3618 correctly, the only supported
> authentication mechanism is TCP-MD5 (RFC 2385), and there have been no
> updates to RFC 3618 that are indicated in the RFC database. However,
> RFC 2385 is obsoleted by RFC 5925 (TCP-AO). Can TCP-AO be used with
> MSDP? What protocol elements or operation are controlled by the
> "authentication" container? What algorithms are valid for use with the
> "password" case? RFC 8177 is the sole reference for both the
> "key-chain" leaf and the "password" case, but that does not seem a
> sufficient reference from which to implement.

Yes, more clarity is needed.

MSDP is only specified to work with TCP-MD5.  While TCP-AO could be a
possibility, there is no current specification or implementation (that
I know of) that goes beyond MD5.

> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> This document (and the YANG module) lists six authors, which is more
> than the typical five and would normally spark some discussion. I do
> see that the shepherd writeup indicates that all six members of the
> design team were quite active, and presume that this indicates that it
> is appropriate to have the larger author count than is typically seen.

It is.