On Wed, May 10, 2023, 2:10 PM Les Ginsberg (ginsberg)
wrote:
>
> Watson -
>
> Where are we with this discission?
> Have my responses clarified things sufficiently or do you still have
> unresolved issues?
Apologies for the delay. I think I understand the issue. If all
devices are in one administ
Watson -
Where are we with this discission?
Have my responses clarified things sufficiently or do you still have unresolved
issues?
Thanx.
Les
> -Original Message-
> From: Les Ginsberg (ginsberg)
> Sent: Friday, May 5, 2023 4:54 PM
> To: Watson Ladd
> Cc: secdir ; draft-ietf-lsr-
Watson -
Please see LES2: inline.
> -Original Message-
> From: Watson Ladd
> Sent: Friday, May 5, 2023 3:32 PM
> To: Les Ginsberg (ginsberg)
> Cc: secdir ; draft-ietf-lsr-rfc8919bis@ietf.org; last-
> c...@ietf.org; lsr@ietf.org
> Subject: Re: Secdir last call review of draft-ietf-ls
On Thu, May 4, 2023, 9:20 PM Les Ginsberg (ginsberg) wrote:
>
> Watson -
>
> Before responding to your comments, I point out that this is a bis of RFC
> 8919 - and it makes no changes to the protocol extensions defined in RFC 8919
> - it only provides some clarifications so that readers/implemen
Watson -
Before responding to your comments, I point out that this is a bis of RFC 8919
- and it makes no changes to the protocol extensions defined in RFC 8919 - it
only provides some clarifications so that readers/implementors are more likely
to have a common understanding.
The Security secti
Reviewer: Watson Ladd
Review result: Has Issues
Dear all,
I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG. These comments were written primarily for the benefit of the
security area directors. Document e
