So, page 21 says:
> ... This provides an
> earliest date which is reasonable. Call this the current
> reasonable date (CRD). This value SHOULD NOT be stored in any
> way, and applies to the current Registration attempt only.
> Subsequent attempts MUST follow this proceedure ag
On 27/03/2018 10:47, Michael Richardson wrote:
>
> Brian E Carpenter wrote:
> > On 27/03/2018 08:11, Michael Richardson wrote:
> > ...
> >>
> >> > d) Add section to request brksi-proxy and brski-registrar to
> >> > IANA service name registry.
> >>
> >> I'm still not su
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and
Approach WG of the IETF.
Title : Bootstrapping Remote Secure Key Infrastructures
(BRSKI)
Authors : Max Pri
Brian E Carpenter wrote:
> On 27/03/2018 08:11, Michael Richardson wrote:
> ...
>>
>> > d) Add section to request brksi-proxy and brski-registrar to
>> > IANA service name registry.
>>
>> I'm still not sure I understand the why of dns-sd discovery in an ANI
>> envi
Brian E Carpenter wrote:
> I definitely recommend replacing lower-case "may" in a case like
> the one below.
Agreed.
> Perhaps:
>>> , and MUST NOT be
>>> enabled unless the JRC indicates support for them
Changed.
--
Michael Richardson , Sandelman Software Works
-= IPv6
Final comments/actions on Toerless' awesome review.
The -13 is coming out soon, but we have 13 issues to resolve still.
>
-
> Section 8)
> a) First paragraph: Unvailable MASA is not a security but an
> o
On one point only:
On 27/03/2018 08:11, Michael Richardson wrote:
>
> > d) Add section to request brksi-proxy and brski-registrar to
> > IANA service name registry.
>
> I'm still not sure I understand the why of dns-sd discovery in an ANI
> environment.
That's a discussion on its o
Comments on section 5, 6 and 7.
> --
> Section 5.4
> a) See comment for section 2.4.4 for where i think the first paragraph
> description should be.
There isn't a 2.4.4, so I'm not really sure I understand wh