Re: [Last-Call] Secdir last call review of draft-ietf-spring-segment-routing-policy-14

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Benjamin,

Thanks for your review and please check in-line below for responses.


On Tue, 23 Nov 2021 at 23:22, Benjamin Schwartz via Datatracker <noreply@xxxxxxxx> wrote:
Reviewer: Benjamin Schwartz
Review result: Ready

This document is ready with a few minor clarifications.  It does not seem to
require detailed Security Area review.

Section 2.1
"printable ASCII characters": Needs reference to what qualifies as "printable
ASCII".

KT> This made me search around a bit. I've found RFC20 (which doesn't explicitly define it) and then RFC1342 that uses that term. I thought this was a well-known thing and not something that needs additional qualifications or references and happy to put the right reference if one exists.
 

"color is a 32-bit numerical value": specify unsigned?

KT> Yes. Will update in the next update.
 

Section 2.4
"represented as a 4-byte number": In what byte order?

KT> Since this document does not specify an "on the wire protocol" the byte order would be dictated by the system implementing it.
 

Section 9 "Protection": It's not clear who this is protecting from what.
Possible alternative title: "Recovering from segment failure".

KT> Ack. Will change to "Recovering from Network Failures".

Thanks,
Ketan
 
-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux