Reviewer: Joel Halpern
Review result: Ready
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more
Reviewer: Dale Worley
Review result: Ready with Nits
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more
Thanks Christer, that all looks good to me,
Regards
Brian
On 13-Jul-20 20:58, Christer Holmberg wrote:
> Hi Brian,
>
> Thank You for the review! Please see inline.
>
>
> Nits:
> -
>
>>> 4.1. MSRP URI
>>>
>>> transport /= "dc"
>>>
>>> I see that RFC7977 takes a slightly
On 14-Jul-20 02:58, Paul Kyzivat wrote:
> Brian,
>
> On 7/12/20 6:40 PM, Brian Carpenter via Datatracker wrote:
>
>> Nits:
>> -
>>
4.1. MSRP URI
>>
transport /= "dc"
>>
>> I see that RFC7977 takes a slightly different approach to updating the ABNF:
>>
Brian,
On 7/12/20 6:40 PM, Brian Carpenter via Datatracker wrote:
Nits:
-
4.1. MSRP URI
transport /= "dc"
I see that RFC7977 takes a slightly different approach to updating the ABNF:
transport = "tcp" / "ws" / 1*ALPHANUM
The advantage of listing out
Thanks for these notes, Pete. I incorporated these fixes into the -08 (but
apparently neglected to write and say so at the time).
Jon Peterson
Neustar, Inc.
Document: draft-ietf-stir-passport-divert-07
Reviewer: Pete Resnick
Review Date: 2020-01-09
IETF LC End Date: 2019-12-02
Hello Russ and Adam,
On Mon, Jul 13, 2020 at 06:42:09AM -0700, internet-dra...@ietf.org wrote:
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-core-resource-directory/
the newly submitted -25 was uploaded to address the points you've
brought up
Hi Brian,
Thank You for the review! Please see inline.
Nits:
-
>> 4.1. MSRP URI
>>
>> transport /= "dc"
>>
>> I see that RFC7977 takes a slightly different approach to updating the ABNF:
>>
>> transport = "tcp" / "ws" / 1*ALPHANUM
>>
> The advantage of listing out
>
>
Hi Michael,
Yes, that would be great, if possible.
Thank you,
Ines
On Mon, Jul 13, 2020 at 3:56 AM Michael Richardson
wrote:
>
> Ines Robles via Datatracker wrote:
> > 2- Introduction: "reports from implementers suggest..." It would be
> nice to add
> > reference/s here
>
> Well,