[Pals] Re: [Shepherding AD review] review of draft-ietf- pals-ple-07.txt
"Gunter van de Velde \(Nokia\)" <[email protected]> Wed, 9 Oct 2024 09:33:19 +0000
| Newsgroups | gmane.ietf.pwe3 |
|---|---|
| Message-ID | <AS1PR07MB8589CAFAF79C2EB82DA83589E07F2@AS1PR07MB8589.eurprd07.prod.outlook.com> |
--===============0827854846267972274== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_AS1PR07MB8589CAFAF79C2EB82DA83589E07F2AS1PR07MB8589eurp_" --_000_AS1PR07MB8589CAFAF79C2EB82DA83589E07F2AS1PR07MB8589eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thank you Christian and author team, I cross checked the document and everything is as you indicted. I requested= IETF LC. @Stewart Bryant<mailto:[email protected]> Could you update the sheph= erd writeup regarding the update of normative vs informative references? Kind Regards, G/ From: Christian Schmutzer (cschmutz) <[email protected]> Sent: Tuesday, October 8, 2024 11:43 PM To: Gunter van de Velde (Nokia) <[email protected]> Cc: Christian Schmutzer (cschmutz) <[email protected]>; draft-ietf-pals-pl= [email protected]; [email protected] Subject: Re: [Shepherding AD review] review of draft-ietf-pals-ple-07.txt CAUTION: This is an external email. Please be very careful when clicking li= nks or opening attachments. See the URL nok.it/ext for additional informati= on. Hi Gunter, Sorry for the delay. I have processed your comments and uploaded a new vers= ion (-08) of the draft. Also some notes inline below via [cs] Regards Christian On 25.09.2024, at 17:39, Gunter van de Velde (Nokia) <gunter.van_de_velde@n= okia.com<mailto:[email protected]>> wrote: # Gunter Van de Velde, RTG AD, comments for draft-ietf-pals-ple-07 Hi Authors, The review details some questions and some observations that occurred when = going through the document. Many thanks to produce this document and all the work to bring it in the cu= rrent quality technological write-up. The referenced line numbers are derived from the idnits tool: https://author-tools.ietf.org/api/idnits?url=3Dhttps://www.ietf.org/archive= /id/draft-ietf-pals-ple-07.txt #GENERIC COMMENTS #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ## This draft is not an easy read. It has significant very specific technol= ogies and requires rather in-depth understanding. ## I believe that the document is nearly ready for the next step in the IES= G processing pipeline after looking through the mostly editorial comments. #DETAILED COMMENTS #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ## 134 (SAToP) defined in [RFC4553]. The applicability is expanded b= eyond 135 the narrow set of PDH interfaces (T1, E1, T3 and E3) to allow = the 136 transport of signals from many different technologies such as GV> Maybe expand that PDH =3D Plesiochronous Digital Hierarchy (PDH) standa= rd in the terminology section [cs] great catch, thank you. I have added it 382 4. Emulated Services 383 384 This specification does describe the emulation of services fro= m a 385 wide range of technologies such as TDM, Ethernet, Fibre Channe= l or 386 OTN as bit stream or structured bit stream as defined in 387 Section 3.3.3 of [RFC3985] and Section 3.3.4 of [RFC3985]. GV> proposed editorial rewrite: " This specification describes the emulation of services from a wide range of= technologies, such as TDM, Ethernet, Fibre Channel, or OTN, as bit streams= or structured bit streams, as defined in Section 3.3.3 and Section 3.3.4 o= f RFC3985. " [cs] done 661 Over time many different Fibre Channel interface types have be= en 662 specified in FC-PI-x and FC-FS-x standards with a varying set = of 663 characteristics such as optional vs mandatory FEC and single-l= ane vs 664 multi-lane transmission. GV> are FC-PI-x and FC-FS-x mentioned in the reference section? I did not f= ind when searching [cs] the "-x" was meant as a generic references to "-2", "-5", ... I see ho= w this could be misleading. As the previous sentence is already mentioning = the standardisation body (INCITS) I simply reworded the sentence to the fol= lowing without the "-x" "Over time many different Fibre Channel interface types have been specified= with a varying set of characteristics such as optional vs mandatory FEC an= d single-lane vs multi-lane transmission." 680 The PSN-bound IWF is mapping the received 8B/10B code stream = as is 681 into the basic PLE payload. GV> s/as is/directly/ [cs] done 767 Note : the use of rate compensation is for further study. GV> Not sure this comment belongs in a standards track document as written.= Maybe it should say in addition that it is out-of-scope of this draft [cs] done 787 Note: Invalid transmission words typically are a consequence o= f the 788 CE-bound IWF inserting replacement data in case of lost PLE pa= ckets, 789 or if the far-end PSN-bound NSP function did set sync headers = to 11 790 due to uncorrectable FEC errors. GV> What does "set sync headers to 11" exactly mean? is that a value to fil= l into the headers somewhere? [cs] the first 2 bits of a 66B code word are call "sync header" (as per IEE= E 802.3). Values 10 and 01 are valid. 11 and 00 are invalid. 932 When processing the Upper-Layer header of a packet matching a = FIB 933 entry locally instantiated as an End.DX1 SID, N does the follo= wing: 934 935 S01. If (Upper-Layer header type =3D=3D TBA1 (bit-stream) ) { 936 S02. Remove the outer IPv6 header with all its extension he= aders 937 S03. Forward the remaining frame to the IWF I 938 S04. } Else { 939 S05. Process as per {{Section 4.1.1 of RFC8986}} 940 S06. } GV> What confused me was how this exactly fits together with the pseudocode= provided in previous paragraph. Maybe these should be combined for a full understanding of the target logic= (similar as in the appendix of [I-D.draft-ietf-spring-srv6-srh-compression= ] [cs] I reworded to "when processing the next (Upper-Layer) header" so it cl= early aligns with line S05 in the previous pseudo code block 983 * RSV 984 985 These bits are reserved for future use. This field MUST be= set to 986 zero by the sender and ignored by the receiver. GV> Maybe it is useful to give the following some thoughts. The rfc8126 definition of reserved vs unassigned is followed: Unassigned: Not currently assigned, and available for assignment via documented procedures. While it's generally clear that any values that are not registered are unassigned and available for assignment, it is sometimes useful to explicitly specify that situation. Note that this is distinctly different from "Reserved". Reserved: Not assigned and not available for assignment. Reserved values are held for special uses, such as to extend the namespace when it becomes exhausted. "Reserved" is also sometimes used to designate values that had been assigned but are no longer in use, keeping them set aside as long as other unassigned values are available. Note that this is distinctly different from "Unassigned". Reserved values can be released for assignment by the change controller for the registry (this is often the IESG, for registries created by RFCs in the IETF stream). "Unassigned" (available for assignment) or "Reserved" (not available unless= released by an RFC), as described in RFC 8126. Note: It isn't clear whether "Unused" means "not currently used" or "can ne= ver be used." [cs] We are following the lead of RFC4553, I think its best to keep it as r= eserved. 969 * L 970 971 Set by the PE to indicate that data carried in the payload = is 972 invalid due to an attachment circuit fault. The downstream= PE 973 MUST play out appropriate replacement data. The NSP MAY in= ject an 974 appropriate native fault propagation signal. GV> what does play out exactly mean? (I suspect my english skills confuse m= e) [cs] changed "play out' to "send" Kind Regards, G/ --_000_AS1PR07MB8589CAFAF79C2EB82DA83589E07F2AS1PR07MB8589eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.apple-converted-space {mso-style-name:apple-converted-space;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Aptos",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"en-BE" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea= k-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US">Thank you Christian and author team,<o:p></o:p></spa= n></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US">I cross checked the document and everything is as yo= u indicted. I requested IETF LC.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US"><a id=3D"OWAAM4BE03E17B43A4C4EB3C0A17FEA94C9B2" href= =3D"mailto:[email protected]"><span style=3D"font-family:"Aptos= ",sans-serif;text-decoration:none">@Stewart Bryant</span></a> Could you update the shepherd writeup regarding the update of normative vs= informative references?<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US">Kind Regards,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US">G/ <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt;mso-f= areast-language:EN-US"><o:p> </o:p></span></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo= nt-family:"Calibri",sans-serif">From:</span></b><span lang=3D"EN-= US" style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"> = Christian Schmutzer (cschmutz) <[email protected]> <br> <b>Sent:</b> Tuesday, October 8, 2024 11:43 PM<br> <b>To:</b> Gunter van de Velde (Nokia) <[email protected]>= ;<br> <b>Cc:</b> Christian Schmutzer (cschmutz) <[email protected]>; draft= [email protected]; [email protected]<br> <b>Subject:</b> Re: [Shepherding AD review] review of draft-ietf-pals-ple-0= 7.txt<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding= =3D"0" align=3D"left" width=3D"100%" style=3D"width:100.0%"> <tbody> <tr> <td style=3D"background:#FFB900;padding:5.0pt 2.0pt 5.0pt 2.0pt"> <p class=3D"MsoNormal" style=3D"mso-element:frame;mso-element-frame-hspace:= 2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-el= ement-anchor-horizontal:column;mso-height-rule:exactly"> <span style=3D"color:black"> </span><o:p></o:p></p> </td> <td width=3D"100%" style=3D"width:100.0%;background:#FFF8E5;padding:5.0pt 4= .0pt 5.0pt 12.0pt"> <div> <p class=3D"MsoNormal" style=3D"mso-element:frame;mso-element-frame-hspace:= 2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-el= ement-anchor-horizontal:column;mso-height-rule:exactly"> <b><span style=3D"color:#222222">CAUTION:</span></b><span style=3D"color:#2= 22222"> This is an external email. Please be very careful when clicking lin= ks or opening attachments. See the URL nok.it/ext for additional informatio= n.<o:p></o:p></span></p> </div> </td> </tr> </tbody> </table> <p> <o:p></o:p></p> <div> <p class=3D"MsoNormal">Hi Gunter, <o:p></o:p></p> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">Sorry for the delay. I have processed your comments = and uploaded a new version (-08) of the draft.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">Also some notes inline below via [cs]<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">Regards<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal">Christian <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal">On 25.09.2024, at 17:39, Gunter van de Velde (Nokia)= <<a href=3D"mailto:[email protected]">gunter.van_de_velde@n= okia.com</a>> wrote:<o:p></o:p></p> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt"># Gu= nter Van de Velde, RTG AD, comments for draft-ietf-pals-ple-07</span><span = style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"> <o:p></o:p></= span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Hi Authors,<br> <br> <br> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">The review details = some questions and some observations that occurred when going through the d= ocument.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"> <o:p></o:p></= span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Many= thanks to produce this document and all the work to bring it in the curren= t quality technological write-up.</span><span style=3D"font-size:11.0pt"><o= :p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">T</s= pan><span lang=3D"en-BE" style=3D"font-size:11.0pt">he referenced line numb= ers are derived from the idnits tool:</span><span style=3D"font-size:11.0pt= "><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt"><a h= ref=3D"https://author-tools.ietf.org/api/idnits?url=3Dhttps://www.ietf.org/= archive/id/draft-ietf-pals-ple-07.txt"><span style=3D"color:#467886">https:= //author-tools.ietf.org/api/idnits?url=3Dhttps://www.ietf.org/archive/id/dr= aft-ietf-pals-ple-07.txt</span></a></span><span style=3D"font-size:11.0pt">= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">#GEN= ERIC COMMENTS</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">#=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span><span style=3D"font-siz= e:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">## T= his d</span><span lang=3D"EN-US" style=3D"font-size:11.0pt">raft<span class= =3D"apple-converted-space"> </span></span><span lang=3D"en-BE" style= =3D"font-size:11.0pt">is not an easy read. It has significant very specific technologies and requires rather in-depth understanding.</sp= an><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">## I= believe that the document is nearly ready for the next step in the IESG pr= ocessing pipeline after looking through the mostly editorial comments.</spa= n><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">#DET= AILED COMMENTS</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p= > </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">#=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span><span style=3D"font-= size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">##</= span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">134&= nbsp; (SAToP) defined in [RFC455= 3]. The applicability is expanded beyond</span><span style=3D"font-si= ze:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">135&= nbsp; the narrow set of PDH inte= rfaces (T1, E1, T3 and E3) to allow the</span><span style=3D"font-size:11.0= pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">136&= nbsp; transport of signals from = many different technologies such as</span><span style=3D"font-size:11.0pt">= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; Maybe expand that PDH =3D Plesiochronous Digital Hierarchy (PDH) standar= d</span><span class=3D"apple-converted-space"><span lang=3D"EN-US" style=3D= "font-size:11.0pt"> </span></span><span lang=3D"EN-US" style=3D"font-s= ize:11.0pt">in the terminology section</span><span style=3D"font-size:11.0pt"><o:p></o:p>= </span></p> </div> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] great catch, thank you. I have added it <o= :p></o:p></p> </div> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">382&= nbsp; 4. Emulated Services</span><span = style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">383<= /span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">384&= nbsp; This specification does de= scribe the emulation of services from a</span><span style=3D"font-size:11.0= pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">385&= nbsp; wide range of technologies= such as TDM, Ethernet, Fibre Channel or</span><span style=3D"font-size:11.= 0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">386&= nbsp; OTN as bit stream or struc= tured bit stream as defined in</span><span style=3D"font-size:11.0pt"><o:p>= </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">387&= nbsp; Section 3.3.3 of [RFC3985]= and Section 3.3.4 of [RFC3985].</span><span style=3D"font-size:11.0pt"><o:= p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; proposed editorial rewrite:</span><span style=3D"font-size:11.0pt"><o:p>= </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&quo= t;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">This= specification describes the emulation of services from a wide range of tec= hnologies, such as TDM, Ethernet, Fibre Channel, or OTN, as bit streams or = structured bit streams, as defined in Section 3.3.3 and Section 3.3.4 of RFC3985.</span><span style=3D"font-size= :11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&quo= t;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] done<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><br> <br> </span><o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">661&= nbsp; Over time many different F= ibre Channel interface types have been</span><span style=3D"font-size:11.0p= t"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">662&= nbsp; specified in FC-PI-x and F= C-FS-x standards with a varying set of</span><span style=3D"font-size:11.0p= t"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">663&= nbsp; characteristics such as op= tional vs mandatory FEC and single-lane vs</span><span style=3D"font-size:1= 1.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">664&= nbsp; multi-lane transmission.</= span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; are FC-PI-x and FC-FS-x mentioned in the reference section? I did not fi= nd when searching</span><span style=3D"font-size:11.0pt"><o:p></o:p></span>= </p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] the “-x” was meant as a generic ref= erences to “-2”, “-5”, … I see how this could= be misleading. As the previous sentence is already mentioning the standard= isation body (INCITS) I simply reworded the sentence to the following witho= ut the “-x"<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">“Over time many different Fibre Channel interf= ace types have been specified with a varying set of characteristics such as= optional vs mandatory FEC and single-lane vs multi-lane transmission.̶= 1;<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt">680 = The PSN-bound IWF is mapping the received 8B/10B code s= tream as is<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">681&= nbsp; into the basic PLE payload= .</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; s/as is/directly/</span><span style=3D"font-size:11.0pt"><o:p></o:p></sp= an></p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] done<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">767&= nbsp; Note : the use of rate com= pensation is for further study.</span><span style=3D"font-size:11.0pt"><o:p= ></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; Not sure this comment belongs in a standards track document as written. = Maybe it should say in addition that it is out-of-scope of this draft</span= ><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] done<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">787&= nbsp; Note: Invalid transmission= words typically are a consequence of the</span><span style=3D"font-size:11= .0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">788&= nbsp; CE-bound IWF inserting rep= lacement data in case of lost PLE packets,</span><span style=3D"font-size:1= 1.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">789&= nbsp; or if the far-end PSN-boun= d NSP function did set sync headers to 11</span><span style=3D"font-size:11= .0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">790&= nbsp; due to uncorrectable FEC e= rrors.</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; What does "set sync headers to 11" exactly mean? is that a val= ue to fill into the headers somewhere?</span><span style=3D"font-size:11.0p= t"><o:p></o:p></span></p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] the first 2 bits of a 66B code word are call &#= 8220;sync header” (as per IEEE 802.3). Values 10 and 01 are valid. 11= and 00 are invalid.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"> </span><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">932&= nbsp; When processing the Upper-= Layer header of a packet matching a FIB</span><span style=3D"font-size:11.0= pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">933&= nbsp; entry locally instantiated= as an End.DX1 SID, N does the following:</span><span style=3D"font-size:11= .0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">934<= /span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">935&= nbsp; S01. If (Upper-Layer heade= r type =3D=3D TBA1 (bit-stream) ) {</span><span style=3D"font-size:11.0pt">= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">936&= nbsp; S02. Rem= ove the outer IPv6 header with all its extension headers</span><span style= =3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">937&= nbsp; S03. For= ward the remaining frame to the IWF I</span><span style=3D"font-size:11.0pt= "><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">938&= nbsp; S04. } Else {</span><span = style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">939&= nbsp; S05. Pro= cess as per {{Section 4.1.1 of RFC8986}}</span><span style=3D"font-size:11.= 0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">940&= nbsp; S06. }</span><span style= =3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; What confused me was how this exactly fits together with the pseudocode = provided in previous paragraph.</span><span style=3D"font-size:11.0pt"><o:p= ></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">Mayb= e these should be combined for a full understanding of the target logic (si= milar as in the appendix of [I-D.draft-ietf-spring-srv6-srh-compression]</s= pan><span style=3D"font-size:11.0pt"> <o:p></o:p></span></p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">[cs] I reworded to “when processing the next (= Upper-Layer) header” so it clearly aligns with line S05 in the previo= us pseudo code block <o:p></o:p></p> </div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">983&= nbsp; * RSV</span><span st= yle=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">984<= /span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">985&= nbsp; These bi= ts are reserved for future use. This field MUST be set to</span><span= style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">986&= nbsp; zero by = the sender and ignored by the receiver.</span><span style=3D"font-size:11.0= pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; Maybe it is useful to give the following some thoughts.</span><span styl= e=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">The = rfc8126 definition of reserved vs unassigned is followed:</span><span style= =3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; Unassigned: Not currently assigned, and av= ailable for assignment</span><span style=3D"font-size:11.0pt"><o:p></o:p></= span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; via document= ed procedures. While it's generally clear that</span><span style=3D"f= ont-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; any values t= hat are not registered are unassigned and</span><span style=3D"font-size:11= .0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; available fo= r assignment, it is sometimes useful to</span><span style=3D"font-size:11.0= pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; explicitly s= pecify that situation. Note that this is</span><span style=3D"font-si= ze:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; distinctly d= ifferent from "Reserved".</span><span style=3D"font-size:11.0pt">= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; Reserved: Not assigned and not available f= or assignment.</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p= > </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; Reserved val= ues are held for special uses, such as to extend</span><span style=3D"font-= size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; the namespac= e when it becomes exhausted. "Reserved" is also</span><span= style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; sometimes us= ed to designate values that had been assigned</span><span style=3D"font-siz= e:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; but are no l= onger in use, keeping them set aside as long as</span><span style=3D"font-s= ize:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; other unassi= gned values are available. Note that this is</span><span style=3D"fon= t-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; distinctly d= ifferent from "Unassigned".</span><span style=3D"font-size:11.0pt= "><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; Reserved val= ues can be released for assignment by the change</span><span style=3D"font-= size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; controller f= or the registry (this is often the IESG, for</span><span style=3D"font-size= :11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p; registries c= reated by RFCs in the IETF stream).</span><span style=3D"font-size:11.0pt">= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&quo= t;Unassigned" (available for assignment) or "Reserved" (not = available unless released by an RFC), as described in RFC 8126.</span><span= style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">Note= : It isn't clear whether "Unused" means "not currently used&= quot; or "can never be used."</span><span style=3D"font-size:11.0= pt"><o:p></o:p></span></p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] We are following the lead of RFC4553, I think i= ts best to keep it as reserved.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt">969 = * L<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">970<= /span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">971&= nbsp; Set by t= he PE to indicate that data carried in the payload is</span><span style=3D"= font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">972&= nbsp; invalid = due to an attachment circuit fault. The downstream PE</span><span sty= le=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">973&= nbsp; MUST pla= y out appropriate replacement data. The NSP MAY inject an</span><span= style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">974&= nbsp; appropri= ate native fault propagation signal.</span><span style=3D"font-size:11.0pt"= ><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"en-BE" style=3D"font-size:11.0pt">GV&g= t; what does play out exactly mean? (</span><span lang=3D"EN-US" style=3D"f= ont-size:11.0pt">I suspect</span><span class=3D"apple-converted-space"><spa= n lang=3D"en-BE" style=3D"font-size:11.0pt"> </span></span><span lang= =3D"en-BE" style=3D"font-size:11.0pt">my english skills confuse me)</span><span style=3D"font-size:11.0pt"><o:p></o= :p></span></p> </div> </blockquote> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <p class=3D"MsoNormal">[cs] changed “play out’ to “send&q= uot;<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs= p;</span><span style=3D"font-size:11.0pt">Kind Regards,<o:p></o:p></span></= p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">G/</= span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> </div> </blockquote> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </div> </div> </body> </html> --_000_AS1PR07MB8589CAFAF79C2EB82DA83589E07F2AS1PR07MB8589eurp_-- --===============0827854846267972274== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGFscyBtYWls aW5nIGxpc3QgLS0gcGFsc0BpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IHBhbHMtbGVhdmVAaWV0Zi5vcmcK --===============0827854846267972274==--