Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Huub,
Please, see inline.

Thanks,
Nabil

On 1/16/13 5:17 AM, "Huub van Helvoort" <huubatwork@xxxxxxxxx> wrote:

>Hello Nabil,
>
>You replied:
>
>> I will folloup on the other emails. Just catching up in reverse order.
>
> > RDI (Reverse defect indication) is what is used in RFC 6310 to indicate
>> failure in the rverse direction from the failure, and this document is
>> aligned with that.
>
>RDI is used to indicate that the *remote* end has detected a defect
>in the forward direction from local node towards the remote node.
>In the reverse direction (from remote node to local node) there
>is *no* defect. Expanding RDI as Reverse Defect Indication will
>put people on the wrong foot.

<NB2>  CA Reverse defect indication is a logical definition in RFC 6310.
The mechanism used depends on the technology used. Here is what is in RFC
6310 and also in the draft in synergy with RFC 6310:

          Forward defect indication corresponds to the logical OR of:

* Local Attachment Circuit (ingress) Receive Fault,

* Local PSN-facing PW (egress) Transmit Fault, and

* PW Not Forwarding.

Reverse defect indication corresponds to the logical OR of:

* Local Attachment Circuit (egress) Transmit Fault and

* Local PSN-facing PW (ingress) Receive Fault.


Are you sating that there is a problem here, with RFC6310?
<NB2> 


>
>> At the same time, RDI as Remote defect indication is
>> what is used for Ethernet CFM, so the attemot here is to call out
>> the acronyms used and in this case it is the same acronym that
>>correspond
>> to two different terminologies, each with its own context identified.

>
>The same RFC6310 refers to G.775 and in appendix A.2 to ATM which both
>expand RDI into Remote Defect Indiction. And this expansion is used
>several times in RFC6310.
>The additional "for Continuity Check Message" is never used in any
>of these.
<NB> CCM is ised in the Ethernet part which is this draft in here.
Ethernet is not covered in RFC 6310.
>
>So I strongly suggest to expand RDI *only* as:
>"Remote Defect Indication"
>to avoid creating any further confusion.

<NB> Please, see above. There are different contexts per above where the
expanded terminology is applied. Are you suggesting still using Reverse
Defect Indication per above where needed but not to abbreviate it? RDI as
Remote Defect Indication part of Ethernet CFM is already there.
>
>Regards, Huub.
>
>
>




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]