Re: [RTG-DIR] RtgDir Review: draft-ietf-mpls-ri-rsvp-frr-05

[<[e-mail]>]

Hi Chandra,

Your response seems to summarize section 4.6.2.1. about the "downstream
direction", which is fine. My comment below is about section 4.6.2.2.
which describes the "upstream direction": how could an RSVP-TE message
sent to a Phop be a Path instead of a Resv? Am I missing something?

Cheers,

Julien


On 20/06/2019 17:08, Chandrasekar Ramachandran wrote:
> Hi Julien,
> Please refer inline.
>
>
> Juniper Internal
>
>> -----Original Message-----
>> From: [e-mail] <[e-mail]>
>> Sent: Thursday, June 20, 2019 7:38 PM
>>
>> Hi Chandra,
>>
>> Thanks for the update. I've just taken a look at the diff: it looks fine, with an
>> improved MUST/SHOULD ratio. I haven't checked all nits, but it seems you
>> missed a key one in section 4.6.2.2., leaving a Path message when talking
>> about upstream (see below).
> [Chandra] The text "carried in the Path to" is intended because the expected outcome is not to apply long refresh in the two hop neighborhood. That is, if the Phop node (say node X) does not support the extensions, then two nodes downstream of node X must use backward compatible refresh interval. This will enable the NP-MP of node X to time out the path state normally when the refresh timeout expires.
>
> Thanks,
> Chandra.
>
>> Cheers,
>>
>> Julien
>>
>>
>> On 20/06/2019 15:42, Chandrasekar Ramachandran wrote:
>>> [...]
>>>
>>>> -----Original Message-----
>>>> From: [e-mail] <[e-mail]>
>>>> Sent: Thursday, April 11, 2019 10:03 PM
>>>>
>>>> - s/in TIME_VALUES object carried in PATH to default value/in the
>>>> TIME_VALUES object carried in the *Resv* message to a default value/
>>
>> ______________________________________________________________
>> ___________________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites
>> ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez
>> le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les
>> messages electroniques etant susceptibles d'alteration, Orange decline
>> toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>> information that may be protected by law; they should not be distributed,
>> used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete
>> this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been
>> modified, changed or falsified.
>> Thank you.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.