Re: [Asap] Publication has been requested for draft-ietf-asap-siptrunkingcapability-link-02

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 07 March 2023 05:31 UTC

MIME-Version: 1.0
References: <167674622497.20189.12571114334635610827@ietfa.amsl.com> <CAL0qLwaczqu3EZyEEKjOvAyKnUccMeR_3DNNV8=fJSL4z+YWZA@mail.gmail.com> <DS7PR11MB60382C8C42E01A30EAFE411BC4B39@DS7PR11MB6038.namprd11.prod.outlook.com>
In-Reply-To: <DS7PR11MB60382C8C42E01A30EAFE411BC4B39@DS7PR11MB6038.namprd11.prod.outlook.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 06 Mar 2023 21:30:17 -0800
Message-ID: <CAL0qLwbuRKi-p3DM26F6J9Ntr4GjHgttUL1+b5-gfVBg5q7sXg@mail.gmail.com>
To: "Derek Engi (deengi)" <deengi@cisco.com>
Cc: "asap-chairs@ietf.org" <asap-chairs@ietf.org>, "asap@ietf.org" <asap@ietf.org>, "mahoney@nostrum.com" <mahoney@nostrum.com>
Content-Type: multipart/alternative; boundary="000000000000bf074105f648b550"
Archived-At: <https://mailarchive.ietf.org/arch/msg/asap/mBjResrBSpDoeZdoZmsJX3myMUA>
Subject: Re: [Asap] Publication has been requested for draft-ietf-asap-siptrunkingcapability-link-02
Precedence: list

Hi,

I think one of your early non-Abstract references to "capability set"
should include a direct reference to I-D.ietf-asap-sip-auto-peer just so
the reader knows where to go looking.  Leaving it for just the References
section isn't as direct as people probably expect it to be.

Yes, please submit a new version with the minor changes, and I'll request
Last Call when I see it.

-MSK

On Fri, Mar 3, 2023 at 7:30 AM Derek Engi (deengi) <deengi@cisco.com> wrote:

> Hi Murray, thank you for your review and the feedback. I’ve put our
> responses inline below.
>
>
>
> One question: In preparation for IESG review, should we publish a new
> version of this draft? At this point we have only two minor edits in the
> queue (updating acknowledgments & adding reference to SIP).
>
>
>
> Thanks,
>
> Derek
>
>
>
> --
>
> Derek Engi
>
> deengi@cisco.com
>
>
>
>
>
> *From: *Asap <asap-bounces@ietf.org> on behalf of Murray S. Kucherawy <
> superuser@gmail.com>
> *Date: *Monday, February 27, 2023 at 4:03 AM
> *To: *asap-chairs@ietf.org <asap-chairs@ietf.org>
> *Cc: *asap@ietf.org <asap@ietf.org>, mahoney@nostrum.com <
> mahoney@nostrum.com>
> *Subject: *Re: [Asap] Publication has been requested for
> draft-ietf-asap-siptrunkingcapability-link-02
>
> Hi, thanks for sending this along.  Just a couple of questions:
>
>
>
> Where is the layout of a capability set document specified?  If as a
> client I am going to request one, I should know how to parse and apply the
> answer.
>
>
>
> <DE> The capability set document is defined in the ASAP draft (
> https://datatracker.ietf.org/doc/html/draft-ietf-asap-sip-auto-peer) that
> we have referenced informatively. This draft simply registers with IANA the
> link relation that document (and potentially others in the future) makes
> use of.
>
>
>
> Also, I think this should include at least an informative reference to SIP
> itself.
>
>
>
> <DE> Agreed, we'll include an inline reference to RFC3261.
>
>
>
> -MSK
>
>
>
> On Sat, Feb 18, 2023 at 10:50 AM Jean Mahoney via Datatracker <
> noreply@ietf.org> wrote:
>
> Jean Mahoney has requested publication of
> draft-ietf-asap-siptrunkingcapability-link-02 as Informational on behalf of
> the ASAP working group.
>
> Please verify the document's state at
> https://datatracker.ietf.org/doc/draft-ietf-asap-siptrunkingcapability-link/
>
>

[Asap] Publication has been requested for draft-i… Jean Mahoney via Datatracker
Re: [Asap] Publication has been requested for dra… Murray S. Kucherawy
Re: [Asap] Publication has been requested for dra… Derek Engi (deengi)
Re: [Asap] Publication has been requested for dra… Murray S. Kucherawy
Re: [Asap] Publication has been requested for dra… Derek Engi (deengi)