On 10/30/18 08:05, Peter Psenak wrote:
>>
>> I'm going to be pedantic here. According to RFC7770, when a new OSPF
>> Router
>> Information LSA TLV is defined, the spec needs to explicitly state if
>> it's
>> applicable to OSPFv2, v3, or both. While you reference the TLVs from
>> draft-ietf-ospf-s
On Wed, Oct 31, 2018 at 01:21:14AM +, Acee Lindem (acee) wrote:
> Hi Ben,
>
> On 10/30/18, 9:09 PM, "Benjamin Kaduk" wrote:
>
> On Tue, Oct 30, 2018 at 02:28:12PM +, Acee Lindem (acee) wrote:
> > Hi Ben,
> >
> > On 10/30/18, 10:08 AM, "Benjamin Kaduk" wrote:
> >
Hi Ben,
On 10/30/18, 9:09 PM, "Benjamin Kaduk" wrote:
On Tue, Oct 30, 2018 at 02:28:12PM +, Acee Lindem (acee) wrote:
> Hi Ben,
>
> On 10/30/18, 10:08 AM, "Benjamin Kaduk" wrote:
>
> Hi Acee,
>
> On Thu, Oct 25, 2018 at 01:51:42PM +, Acee
On Tue, Oct 30, 2018 at 03:33:21PM +, Acee Lindem (acee) wrote:
> Hi Les,
>
> On 10/30/18, 11:15 AM, "Les Ginsberg (ginsberg)" wrote:
>
> Acee -
>
> > > Section 3.2
> > >
> > > "When a router receives multiple overlapping ranges, it MUST
> > >
On Tue, Oct 30, 2018 at 02:28:12PM +, Acee Lindem (acee) wrote:
> Hi Ben,
>
> On 10/30/18, 10:08 AM, "Benjamin Kaduk" wrote:
>
> Hi Acee,
>
> On Thu, Oct 25, 2018 at 01:51:42PM +, Acee Lindem (acee) wrote:
> > Hi Ben,
> >
> > On 10/25/18, 8:22 AM, "Benjamin Ka
In preparation for requesting publication, I’m making a second IPR call on the
subject document.
Are you aware of any IPR that applies to draft-ietf-ospf-xaf-te?
If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
3979, 4879, 3669 and 5378 for more details).
There ar
Hi Les,
On 10/30/18, 11:15 AM, "Les Ginsberg (ginsberg)" wrote:
Acee -
> > Section 3.2
> >
> > "When a router receives multiple overlapping ranges, it MUST
> >conform to the procedures defined in
> >[I-D.ietf-spring-segment-routin
Acee -
> > Section 3.2
> >
> > "When a router receives multiple overlapping ranges, it MUST
> >conform to the procedures defined in
> >[I-D.ietf-spring-segment-routing-mpls]."
> >
> > It would be useful to include a section pointer here. I think your
>
Hi Peter, Joe, et al,
On 10/30/18, 8:05 AM, "Peter Psenak (ppsenak)" wrote:
Hi Joe,
thanks for your review, please see inline (##PP):
On 26/10/18 21:42 , Joe Clarke wrote:
> Reviewer: Joe Clarke
> Review result: Has Nits
>
> I have been assigned to review
Hi Ben,
On 10/30/18, 10:08 AM, "Benjamin Kaduk" wrote:
Hi Acee,
On Thu, Oct 25, 2018 at 01:51:42PM +, Acee Lindem (acee) wrote:
> Hi Ben,
>
> On 10/25/18, 8:22 AM, "Benjamin Kaduk" wrote:
>
> Benjamin Kaduk has entered the following ballot position f
Hi Acee,
On Thu, Oct 25, 2018 at 01:51:42PM +, Acee Lindem (acee) wrote:
> Hi Ben,
>
> On 10/25/18, 8:22 AM, "Benjamin Kaduk" wrote:
>
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-ospf-lls-interface-id-08: No Objection
>
> When responding, p
Hi Joe,
thanks for your review, please see inline (##PP):
On 26/10/18 21:42 , Joe Clarke wrote:
Reviewer: Joe Clarke
Review result: Has Nits
I have been assigned to review
draft-ietf-ospf-ospfv3-segment-routing-extensions on behalf of the ops
directorate. This document defines OSPFv3 extensi
12 matches
Mail list logo