Hi Jeffrey, Alvaroo,
2015-09-28, Jeffrey (Zhaohui) Zhang:
Alvaro,
> I-D.ietf-bess-ir and I-D.ietf-bess-mvpn-extranet should be Normative
References.
I thought about this further, and would like to keep them both as
informational for the following reasons.
The extranet draft is referred to in the draft as following:
… The label may be shared
with other P-tunnels, subject to the anti-ambiguity rules for
extranet [I-D.ietf-bess-mvpn-extranet
<https://tools.ietf.org/html/draft-ietf-bess-mvpn-bidir-ingress-replication-02#ref-I-D.ietf-bess-mvpn-extranet>].
Both extranet and label sharing are optional, not required for
implementing the procedures in this draft.
I agree with that.
To make it more obvious that this is an informative comment, I think you
could rewrite as: "These specifications do not prevent sharing of labels
between P-tunnels (note that other specs put constraints on how that can
be done, such as [I-D.ietf-bess-mvpn-extranet
<https://tools.ietf.org/html/draft-ietf-bess-mvpn-bidir-ingress-replication-02#ref-I-D.ietf-bess-mvpn-extranet>])".
As for draft-ietf-bess-ir: RFC 6514 specifies the use of IR P-tunnels,
though there are some problems with RFC 6514's specification of IR
P-tunnels, which are addressed in detail in draft-ietf-bess-ir.
Draft-ietf-bess-mvpn-bidir-ingress-replication explains how to support
a VPN customer's use of BIDIR-PIM when the service provider uses IR
P-tunnels, but it doesn't really depend on those details specified in
draft-ietf-bess-ir. Thus draft-ietf-bess-ir should not be a normative
reference for it.
Given that draft-ietf-bess-ir updates RFC6514/RFC6513 which our draft
depends on Normatively, we might as well avoid mentioning it; making it
a Normative ref would not buy much (but would delay publication until
draft-ietf-bess-ir is published).
Since its helpful to remind the reader of its existence, I would think
it's good to keep it, and Informative is fine.
Best,
-Thomas
_________________________________________________________________________________________________________________________
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.
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
