Hi Tobias/Nick,
We need to check how we cite some of the drafts in draft-ietf-grow-bgpopsecupd.
I think you already know but "Normative references specify documents that must
be read to understand or implement the technology in the new RFC, or whose
technology must be present for the technology in the new RFC to work".
With that in mind, draft-ietf-sidrops-avoid-rpki-state-in-bgp should be listed
as Informative as the only mention is in an example:
CURRENT:
* NLRI carried on BGP MUST NOT be enriched with transitive
attributes subject to change independent of the underlying NLRI,
e.g., encoding RPKI validation state in transitive attributes
[I-D.draft-ietf-sidrops-avoid-rpki-state-in-bgp].
For ietf-grow-routing-ops-sec-inform and draft-ietf-grow-routing-ops-terms, I'm
a little bit puzzled how we cite them:
CURRENT:
Instead, readers MAY refer to the most recent non expired draft of
[I-D.draft-ietf-grow-routing-ops-sec-inform] for an updated list of
currently available technology to ensure the above principles, and
the most recent non expired draft of
[I-D.draft-ietf-grow-routing-ops-terms] for information on currently
used terms and definitions in the context of global routing
operations. Readers MUST NOT rely on expired versions of these I-Ds.
If no most recent non-expired version of either I-D is available, the
document MUST be considered to be non-existent.
I don't think the normative language is needed here as these are provided as
additional information for more context. These are not required to understand
or implement draft-ietf-grow-bgpopsecupd. Also, both I-D mentions seems to be
out of context in a security considerations section. Did I miss something?
Can we please rework this part to avoid creating normative dependency that
would hinder the publication of draft-ietf-grow-bgpopsecupd?
One nit, please s/I-D.draft/I-D. through the draft.
Thank you.
Cheers,
Med
____________________________________________________________________________________________________________
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.
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
