Hi Melchior,
These words are intentionally lower-case and do not carry RFC 2119 or 8174
weight.
In fact, you won't see any RFC 2119 language, IANA requests or packet formats
in the entire document. So, it could be INFORMATIONAL just as well as it could
be STANDARDS TRACK.
Ron
Juniper Business Use Only
From: Melchior Aelmans <melch...@aelmans.eu>
Sent: Sunday, April 12, 2020 3:59 AM
To: Ron Bonica <rbon...@juniper.net>
Cc: spring@ietf.org
Subject: Re: [spring] FW: New Version Notification for
draft-bonica-spring-sr-mapped-six-01.txt
[External Email. Be cautious of content]
Hi Ron, authors,
Are the "should" and "must" used in the following sentence meant as those
described in
https://tools.ietf.org/html/rfc8174<https://urldefense.com/v3/__https:/tools.ietf.org/html/rfc8174__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiIoJGAK3$>?
To minimize packet length, network operators should use 16-bit SIDs
whenever possible. However, when more than 65,520 SIDs are required,
network operators must use 32-bit SIDs.
In other words the Requirements Language section is missing.
Cheers,
Melchior
On Fri, Apr 10, 2020 at 5:06 PM Ron Bonica
<rbonica=40juniper....@dmarc.ietf.org<mailto:40juniper....@dmarc.ietf.org>>
wrote:
Folks,
Please review and comment.
Ron
Juniper Business Use Only
> -----Original Message-----
> From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>
> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>>
> Sent: Friday, April 10, 2020 10:18 AM
> To: Luay Jalil
> <luay.ja...@one.verizon.com<mailto:luay.ja...@one.verizon.com>>; Gang Chen
> <phdg...@gmail.com<mailto:phdg...@gmail.com>>;
> ext-andrew.als...@liquidtelecom.com<mailto:ext-andrew.als...@liquidtelecom.com>
> <andrew.als...@liquidtelecom.com<mailto:andrew.als...@liquidtelecom.com>>;
> Jen Linkova <fu...@google.com<mailto:fu...@google.com>>;
> ext-andrew.als...@liquidtelecom.com<mailto:ext-andrew.als...@liquidtelecom.com>
> <andrew.als...@liquidtelecom.com<mailto:andrew.als...@liquidtelecom.com>>;
> Daniam Henriques
> <daniam.henriq...@liquidtelecom.com<mailto:daniam.henriq...@liquidtelecom..com>>;
> Ron Bonica
> <rbon...@juniper.net<mailto:rbon...@juniper.net>>; Yuji Kamite
> <y.kam...@ntt.com<mailto:y.kam...@ntt.com>>; Joel Halpern
> <joel.halp...@ericsson.com<mailto:joel.halp...@ericsson.com>>; Shraddha Hegde
> <shrad...@juniper.net<mailto:shrad...@juniper.net>>
> Subject: New Version Notification for draft-bonica-spring-sr-mapped-six-
> 01.txt
>
> [External Email. Be cautious of content]
>
>
> A new version of I-D, draft-bonica-spring-sr-mapped-six-01.txt
> has been successfully submitted by Ron Bonica and posted to the IETF
> repository.
>
> Name: draft-bonica-spring-sr-mapped-six
> Revision: 01
> Title: Segment Routing Mapped To IPv6 (SRm6)
> Document date: 2020-04-10
> Group: Individual Submission
> Pages: 18
> URL:
> https://urldefense.com/v3/__https://www.ietf.org/internet-<https://urldefense.com/v3/__https:/www.ietf.org/internet->
> drafts/draft-bonica-spring-sr-mapped-six-01.txt__;!!NEt6yMaO-
> gk!ReC5D9PqJg9VvhTCWgZN97t18LSeFN2lqDJE-
> 4sfI8tHuQzazw38mDU55l4XfCX4$
> Status:
>
> https://datatracker.ietf.org/doc/draft-bonica-spring-sr-mapped-six<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-bonica-spring-sr-mapped-six__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiGjXv_EV$>
> Htmlized:
> https://tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiFLvKMZ3$>
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-bonica-spring-sr-mapped-six<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-bonica-spring-sr-mapped-six__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiKF1Mz-Y$>
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-bonica-spring-sr-mapped-six-01<https://urldefense.com/v3/__https:/www.ietf.org/rfcdiff?url2=draft-bonica-spring-sr-mapped-six-01__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiLfD7Vb9$>
>
> Abstract:
> This document describes Segment Routing Mapped to IPv6 (SRm6). SRm6
> is a Segment Routing (SR) solution that supports a wide variety of
> use-cases while complying with IPv6 specifications. SRm6 is
> optimized for ASIC-based routers that operate at high data rates.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> tools.ietf.org<https://urldefense.com/v3/__http:/tools.ietf.org__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiMG33FtH$>.
>
> The IETF Secretariat
>
_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!Rgx7CYdsiICBAUWuI6Dy3xSPEH0YemhahBTgQ6NeA8DKEFRymprNFwmDiBIJiR8N$>
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
