Hi Joe,

Thanks for providing an update to this draft. I am good with the changes.

Before proceeding with IETF LC, can the Shepherd’s write-up be updated to 
justify having more than 5 authors on the front page (question #13)?

> On Aug 24, 2025, at 1:18 PM, Mahesh Jethanandani <[email protected]> 
> wrote:
> 
> Hi Joe,
> 
>> On Aug 24, 2025, at 4:38 AM, Joe Clarke (jclarke) <[email protected]> wrote:
>> 
>> Thanks for a quick response. I have uber-level comment/observation for this 
>> draft, and one for the combination of the three drafts, which I will send 
>> separately.
>>  
>> On the question of the number of authors on the first page, RFC 7322 gives 
>> two choices. One is to limit the number of authors to five, or for the 
>> stream approving body, IESG in this case, to consider one or two editors 
>> that will have primary responsibility for the document, with everyone else 
>> listed in the Contributor or Acknowledgement section. Let me know your 
>> preference.
>>  
>> [JMC] My read of 7322 is different than yours.  There is no normative 
>> language here, and it says that the approving body needs to consider if one 
>> or two editors should have primary responsibility of the document.  That 
>> doesn’t mean there are black and white rules on this.  And, in fact, reading 
>> some recent emails on the chairs list, I see that exceptions to the five 
>> authors rule are granted (see RFC8415 as an example).  We still believe this 
>> is a case where an exception is warranted.
>>  
>> Joe
> 
> If the authors want to go down the path of justifying more than five authors 
> on the first page, we will have to start with updating the Shepherd’s 
> write-up, where in question #13, the current answer says N/A. The Shepherd 
> might want to review other documents where such exception was granted to add 
> the text for justification.
> 
> Thanks.


Mahesh Jethanandani
[email protected]






_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to