Re: [Int-dir] [BULK] Intdir telechat review of draft-ietf-idr-flow-spec-v6

[Christoph Loibl <[e-mail]>]

Hi Donald,

Thank you for your review and comments. See my comments inline. I also attached a updated document that contains changes resulting from your comments.

Since the draft submission is closed now I will ask Alvaro to publish the changed document today.

Cheers Christoph


> Section 4: Does the IETF allow direct references into github in the
> main body of a standards track RFC? Looks like all the comparison code
> is in the Appendix. Can the github reference at least be moved to the
> Appendix?
> 
> Section 11.2: As far as I know, there are only normative and
> informational references, not "URIs" references.

This is exactly the same as in rfc5575bis which has been edited by rfc-editors, I think we can leave this for rfc-editors. I see they somehow removed this reference.

> 
> ## Editorial
> Section 1, 1st sentence: "to be also capable of supporting" -> "to
> also support"

Edited as suggested.

> 
> Section 1, 2nd sentence:
> OLD
> This document analyzes the differences of IPv6 [RFC8200] flows
> description from those of traditional IPv4 packets and propose a
> subset of new Border Gateway Protocol [RFC4271] encoding formats to
> enable Dissemination of Flow Specification Rules
> [I-D.ietf-idr-rfc5575bis] for IPv6.

> NEW
> This document analyzes the differences between describing IPv6
> [RFC8200] flows and those of traditional IPv4 packets. It specifies
> new Border Gateway Protocol [RFC4271] encoding formats to enable
> Dissemination of Flow Specification Rules [I-D.ietf-idr-rfc5575bis]
> for IPv6.
> 

Also edited as suggested.

> There are some other minor editorial things like plural/singular
> forms but I assume the RFC Editor will fix those.

Thanks for the comments.

-- 
Christoph Loibl
[e-mail] | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at