Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)

2018-04-10 Thread Di Ma
Hi, Ben,

Thanks for reminding us:-)

Di

> 在 2018年4月10日,02:28,Ben Campbell  写道:
> 
> 
> 
>> On Apr 6, 2018, at 10:06 AM, Spencer Dawkins at IETF 
>>  wrote:
>> 
>> Hi, Di,
>> 
>> On Fri, Apr 6, 2018 at 9:33 AM, Di Ma  wrote:
>> Alissa,
>> 
>> Thanks very much for your comments.
>> 
>> Is BCP 14 exactly the same document as RFC 2119?
>> 
>> It was, until  https://tools.ietf.org/html/rfc8174 was added to BCP 14. 
>> That's the process doc that says readers don't have to figure out whether 
>> "must" is normative, etc.
>> 
>> Spencer, who is not Alissa, but had a second to answer the question
> 
> Also not Alissa (or Spencer), but to extend the answer a bit: RFC 8174 
> includes new boilerplate for treating only the upper case versions as 
> keywords.
> 
> Thanks!
> 
> Ben.



___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr


Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)

2018-04-09 Thread Ben Campbell


> On Apr 6, 2018, at 10:06 AM, Spencer Dawkins at IETF 
>  wrote:
> 
> Hi, Di,
> 
> On Fri, Apr 6, 2018 at 9:33 AM, Di Ma  wrote:
> Alissa,
> 
> Thanks very much for your comments.
> 
> Is BCP 14 exactly the same document as RFC 2119?
> 
> It was, until  https://tools.ietf.org/html/rfc8174 was added to BCP 14. 
> That's the process doc that says readers don't have to figure out whether 
> "must" is normative, etc.
> 
> Spencer, who is not Alissa, but had a second to answer the question

Also not Alissa (or Spencer), but to extend the answer a bit: RFC 8174 includes 
new boilerplate for treating only the upper case versions as keywords.

Thanks!

Ben.


signature.asc
Description: Message signed with OpenPGP
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr


Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)

2018-04-06 Thread Di Ma
Spencer,

Thanks for your explanation. 

Di

> 在 2018年4月6日,23:06,Spencer Dawkins at IETF  写道:
> 
> Hi, Di,
> 
> On Fri, Apr 6, 2018 at 9:33 AM, Di Ma  wrote:
> Alissa,
> 
> Thanks very much for your comments.
> 
> Is BCP 14 exactly the same document as RFC 2119?
> 
> It was, until  https://tools.ietf.org/html/rfc8174 was added to BCP 14. 
> That's the process doc that says readers don't have to figure out whether 
> "must" is normative, etc.
> 
> Spencer, who is not Alissa, but had a second to answer the question



___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr


Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)

2018-04-06 Thread Spencer Dawkins at IETF
Hi, Di,

On Fri, Apr 6, 2018 at 9:33 AM, Di Ma  wrote:

> Alissa,
>
> Thanks very much for your comments.
>
> Is BCP 14 exactly the same document as RFC 2119?


It was, until  https://tools.ietf.org/html/rfc8174 was added to BCP 14.
That's the process doc that says readers don't have to figure out whether
"must" is normative, etc.

Spencer, who is not Alissa, but had a second to answer the question
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr


Re: [sidr] Alissa Cooper's No Objection on draft-ietf-sidr-slurm-07: (with COMMENT)

2018-04-06 Thread Di Ma
Alissa,

Thanks very much for your comments.

Is BCP 14 exactly the same document as RFC 2119?

Di

> 在 2018年4月5日,02:00,Alissa Cooper  写道:
> 
> Alissa Cooper has entered the following ballot position for
> draft-ietf-sidr-slurm-07: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-sidr-slurm/
> 
> 
> 
> --
> COMMENT:
> --
> 
> Please cite BCP 14 rather than RFC 2119, assuming you intend for normative
> keywords to have their normative meaning in uppercase only.
> 
> 
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr



___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr