Dear all,
no, I am not aware of any IPR that applies to this draft.
Regards,
Victor
De: OPSAWG en nombre de Joe Clarke (jclarke)
Enviado: lunes, 22 de marzo de 2021 14:33
Para: opsawg@ietf.org
Asunto: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common
Dear all,
no, I am not aware of any IPR that applies to this draft.
Regards,
Victor
De: OPSAWG en nombre de Joe Clarke (jclarke)
Enviado: lunes, 22 de marzo de 2021 14:34
Para: opsawg@ietf.org
Asunto: [OPSAWG] IPR CALL: draft-ietf-opsawg-l3sm-l3nm
Authors,
From: Joe Clarke (jclarke)
Sent: 22 March 2021 13:12
On 3/22/21 07:15, Wubo (lana) wrote:
> Hi Tom, Joe,
>
> Thanks for your review and comments. The issues will fixed in the next
> revision.
>
> For 'leaf shared-secret', the following text will be added:
> "It is highly recommended that shared
Hi OPSAWG,
no, I am not aware of any IPR that applies to this draft.
Regards,
Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de
Transporte |
Móvil +57 3017026430
Móvil +34 665416074
E-mail samier.barguilgiraldo@telefonica.com
E-mail
Hi OPSAWG,
no, I am not aware of any IPR that applies to this draft.
Regards,
Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de
Transporte |
Móvil +57 3017026430
Móvil +34 665416074
E-mail samier.barguilgiraldo@telefonica.com
E-mail
Re-,
No, I am not aware of any IPR that applies to this draft.
Cheers,
Med
> -Message d'origine-
> De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de Joe
> Clarke (jclarke)
> Envoyé : lundi 22 mars 2021 14:34
> À : opsawg@ietf.org
> Objet : [OPSAWG] IPR CALL:
Hi Joe, all,
No, I am not aware of any IPR that applies to this draft.
Cheers,
Med
> -Message d'origine-
> De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de Joe
> Clarke (jclarke)
> Envoyé : lundi 22 mars 2021 14:33
> À : opsawg@ietf.org
> Objet : [OPSAWG] IPR CALL:
Dear OPSA WG chairs,
no, I am not aware of any IPR that applies to this draft.
Best Regards,
Oscar
-Mensaje original-
De: OPSAWG En nombre de Joe Clarke (jclarke)
Enviado el: lunes, 22 de marzo de 2021 14:34
Para: opsawg@ietf.org
Asunto: [OPSAWG] IPR CALL: draft-ietf-opsawg-l3sm-l3nm
Dear OPSA WG chairs,
no, I am not aware of any IPR that applies to this draft.
Best Regards,
Oscar
-Mensaje original-
De: OPSAWG En nombre de Joe Clarke (jclarke)
Enviado el: lunes, 22 de marzo de 2021 14:33
Para: opsawg@ietf.org
Asunto: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common
Authors, contributors, and WG members, as we are in WGLC for this
document, we want to solicit knowledge of any IPR that may pertain to
the draft-ietf-opsawg-l3sm-l3nm work.
Please state either, "no, I am not aware of any IPR that applies to this
draft" or, "yes, I am aware of IPR that applies
Authors, contributors, and WG members, as we are in WGLC for this
document, we want to solicit knowledge of any IPR that may pertain to
the draft-ietf-opsawg-vpn-common work.
Please state either, "no, I am not aware of any IPR that applies to this
draft" or, "yes, I am aware of IPR that applies
Hello, WG. One of the action items out of the 110 meeting was to put
the L3NM (https://tools.ietf.org/html/draft-ietf-opsawg-l3sm-l3nm-07)
and vpn-common
(https://tools.ietf.org/html/draft-ietf-opsawg-vpn-common-03) documents
through WG LC. The authors have said that these can work independently
On 3/22/21 07:15, Wubo (lana) wrote:
> Hi Tom, Joe,
>
> Thanks for your review and comments. The issues will fixed in the next
> revision.
>
> For 'leaf shared-secret', the following text will be added:
> "It is highly recommended that shared keys are at least 32 characters long
> and
>
Hi Mohit,
Thanks for the review. I will fix the nits in the next revision.
Thanks,
Bo
-邮件原件-
发件人: Mohit Sethi via Datatracker [mailto:nore...@ietf.org]
发送时间: 2021年3月20日 18:25
收件人: gen-...@ietf.org
抄送: draft-ietf-opsawg-tacacs-yang@ietf.org; last-c...@ietf.org;
opsawg@ietf.org
主题:
Hi Tom, Joe,
Thanks for your review and comments. The issues will fixed in the next revision.
For 'leaf shared-secret', the following text will be added:
"It is highly recommended that shared keys are at least 32 characters long and
sufficiently complex with mixed different character types."
15 matches
Mail list logo
