I am not aware of any relevant IPR.
Peter
On 10/04/2019 23:35 , Acee Lindem (acee) wrote:
Authors, Contributors,
Are you aware of any IPR that applies to draft-ietf-isis-te-app-06.txt?
If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Link State Routing WG of the IETF.
Title : OSPF Link Traffic Engineering (TE) Attribute Reuse
Authors : Peter Psenak
Les
LSR Working Group,
This begins a two week WG last call for the subject document. Please enter
your support or objection to the document before 12:00 AM (EDT) on Friday,
April 27th, 2019.
Thanks,
Acee
___
Lsr mailing list
Lsr@ietf.org
I’m not aware of any IPR related to this document.
Thanks.
s.
> On Apr 10, 2019, at 11:35 PM, Acee Lindem (acee) wrote:
>
> Authors, Contributors,
>
> Are you aware of any IPR that applies to draft-ietf-isis-te-app-06.txt?
>
> If so, has this IPR been disclosed in compliance with IETF IPR
Hi Acee,
I'm not aware of any relevant IPR.
thanks,
Peter
On 11/04/2019 18:09 , Acee Lindem (acee) wrote:
Authors, Contributors,
Are you aware of any IPR that applies
to draft-ietf-ospf-te-link-attr-reuse-07?
If so, has this IPR been disclosed in compliance with IETF IPR rules
(see
Authors, Contributors,
Are you aware of any IPR that applies to draft-ietf-ospf-te-link-attr-reuse-07?
If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).
If you are listed as a document author or contributor please respond
I'm not aware of any IPR.
Yours Irrespectively,
John
Juniper Internal
From: Lsr On Behalf Of Acee Lindem (acee)
Sent: Wednesday, April 10, 2019 5:30 PM
To: draft-ietf-isis-te-...@ietf.org
Cc: lsr@ietf.org
Subject: [Lsr] IPR Poll for "IS-IS TE Attributes per application" -
Hi,
I'm not in favour of this draft.
As already mention, I don't see the interest to duplicate TE attributes in new
Extended Link Opaque LSA. For me, it is only a matter of implementation to look
at various place in the OSPF TE Database to take Traffic Engineering
information.
>From an
I am not aware of any relevant IPR.
Les
From: Acee Lindem (acee)
Sent: Thursday, April 11, 2019 9:10 AM
To: draft-ietf-ospf-te-link-attr-re...@ietf.org
Cc: lsr@ietf.org; Ketan Talaulikar (ketant) ; Hannes Gredler
; Acee Lindem (acee)
Subject: IPR Poll for "OSPF Link Traffic Engineering
Hi,
I'm not in favour of this draft.
For me there is no interest to advertises TE attributes per application. TE
attributes are attached to a linkand are agnostics of application. Looking to
listed applications, I don't understand why we need to duplicate TE attributes.
We could perfectly
Hello,
I am not aware of any IPR related to this draft.
Thanks,
Ketan
From: Acee Lindem (acee)
Sent: 11 April 2019 21:40
To: draft-ietf-ospf-te-link-attr-re...@ietf.org
Cc: lsr@ietf.org; Ketan Talaulikar (ketant) ; Hannes Gredler
; Acee Lindem (acee)
Subject: IPR Poll for "OSPF Link Traffic
Hi, Huaimo,
Why do we need to compute a whole backup path and enable flooding at each
hop? In your example, when R0-R2 and R3-R9 fail, R0 (and R3) will find out
that its neighbor R1 (and R2) are no longer on the FT. R0 (and R3) will
then enable temporary flooding on R0-R1 (and R3-R2), which fixes
Acee,
I’m not aware of any IPR that applies to the draft.
Regards,
Jeff
> On Apr 11, 2019, at 18:09, Acee Lindem (acee) wrote:
>
> Authors, Contributors,
>
> Are you aware of any IPR that applies to
> draft-ietf-ospf-te-link-attr-reuse-07?
>
> If so, has this IPR been disclosed in
13 matches
Mail list logo
