IETF Logo Mail Archive

Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs-01.txt

Owen DeLong <owen@delong.com> Mon, 16 November 2015 19:20 UTC

Return-Path: <owen@delong.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED761A8836 for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.686
X-Spam-Level:
X-Spam-Status: No, score=-6.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
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 vsdF19FP3UZj for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:20:04 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id C95F21A8830 for <opsawg@ietf.org>; Mon, 16 Nov 2015 11:20:02 -0800 (PST)
Received: from delong-dhcp229.delong.com (delong-dhcp29 [192.159.10.229]) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tAGJHvfR016208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 16 Nov 2015 11:17:57 -0800
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <D26F8962.5E2B9%evyncke@cisco.com>
Date: Mon, 16 Nov 2015 11:17:57 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA3ADF0B-DF22-40B4-96EB-B92EE6B524A0@delong.com>
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com> <D26F8962.5E2B9%evyncke@cisco.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/L08xYdotOFJf5BeM_RmfiZgPIkM>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 19:20:05 -0000

> On Nov 16, 2015, at 04:27 , Eric Vyncke (evyncke) <evyncke@cisco.com> wrote:
> 
> Important document indeed.
> 
> I have a comment on section 7.1 where "ip" as a protocol (the double
> quotes are from the I-D) is mentioned but does it mean IPv4 or IPv6 or
> both?

Surely one would hope that it’s meaning is contextual to the time of reading
and that today it would mean {IPv4, IPv6} and that sometime in the future,
it will likely mean {IPv6} and beyond that come to mean {IPv6,…}.

> 
> In the same section, may I suggest to describe the syntax of the 'addr'
> field?

Wouldn’t the syntax of the addr field be inherently dependent on the
RFC defining the IP version in question in the previous context?

Owen

v2.23.0 | Report a Bug | By Email