Re: [PWE3] draft-ietf-pwe3-vccv-bfd-03.txt WG last call

[Carlos Pignataro <cpignata at cisco.com>]

Ben,

Many Thanks for your review and comments. Please see inline.

On 3/15/2009 8:13 AM, Ben Niven-Jenkins wrote:
> I have reviewed the document and one substantive comment and a couple of
> editorial ones.
> 
> Section 7 Security Considerations
>    The IP/UDP-encapsulated BFD makes use of the TTL/Hop Limit
>    procedures described in Section 5 of [I-D.ietf-bfd-v4v6-1hop],
>    including the use of the Generalized TTL Security Mechanism (GTSM) as
>    a security mechanism.
> 
> Is use of TTL/hop limit & GTSM mentioned in the body of the draft I don't
> remember seeing it?
> 

Yes, it is mentioned in Section 3.2 somewhat explicitly (mentioning
TTL/Hop Limit but without mentioning GTSM), like this:

      address from the range 0:0:0:0:0:FFFF:127.0.0.0/104.  The
      rationale is explained in Section 2.1 of [RFC4379].  The Time to
      Live/Hop Limit procedures from Section 5 of
      [I-D.ietf-bfd-v4v6-1hop] apply to this encapsulation, and hence
      the TTL/Hop Limit is set to 255.

And an explicit mention of GTSM is omitted, and instead it's inherent to
the use of BFD w/IP 1hop. However, for clarity and completeness, we
should probably add something like the following to the excerpt above:

      address from the range 0:0:0:0:0:FFFF:127.0.0.0/104.  The
      rationale is explained in Section 2.1 of [RFC4379].  The Time to
      Live/Hop Limit procedures from Section 5 of

|                   ^
|                   add "and Generalized TTL Security Mechanism (GTSM) "

      [I-D.ietf-bfd-v4v6-1hop] apply to this encapsulation, and hence
      the TTL/Hop Limit is set to 255.

Would this work?

Additionally, Ack the three editorials below, changes made with your new
text.

Thanks again,

-- Carlos.

> 
> 
> Page 6, Paragraph that begins " When the downstream PE (D-PE) does not
> receive..."
> 
> Replace
> 
> "direction setting the State to Down, and it using Diagnostic code 3"
> 
> With
> 
> "direction, setting the State to Down with Diagnostic code 3"
> 
> 
> Last sentence of section 3.3
> 
> Replace
> 
> "All BFD CV Types are mutually exclusive with the rest"
> 
> With
> 
> "All BFD CV Types are mutually exclusive"
> 
> 
> 2nd paragraph f section 4
> 
> S/ For these cases were multiple/ For these cases where multiple/
> 
> 
> 
> 
> 
> On 09/03/2009 15:08, "BOCCI Matthew" <Matthew.Bocci at alcatel-lucent.com>
> wrote:
> 
>> This is the start of working group last call on
>> draft-ietf-pwe3-vccv-bfd-03.txt
>>
>> This draft can be found at:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-bfd-03.txt
>>
>> The last call will close on Monday 6th April 2009.
>>
>> Please read the document and provide feedback to the PWE3 list.
>>
>> Many thanks to the following, who have also kindly agreed to review the
>> draft and provide comments to the list:
>> Ben Niven-Jenkins
>> Mustapha Aissaoui
>> Luca Martini
>> Yaakov Stein
>>
>> Best regards
>>
>> Matthew
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3 at ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
> 
> _______________________________________________
> pwe3 mailing list
> pwe3 at ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>