mohamed.boucad...@orange.com wrote:
> However, I checked
>
https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-opsawg-pcaplinktype&url_2=https://IETF-OPSAWG-WG.github.io/draft-ietf-opsawg-pcap/draft-ietf-opsawg-pcaplinktype.txt
> and I'm afraid that your main copy override many changes agreed in the
> past. May be I'm not looking in the right branch?
There is definitely a failure on my part to git push after the last posting.
Guy then patched somethings, and I've just dealt with the conflict.
Trailing periods on a bunch of entries.
type 209, name changed.
Some line wrapping changes too.
The table got broken in -02, sorry about that.
https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-opsawg-pcaplinktype-01&url_2=https%3A%2F%2FIETF-OPSAWG-WG.github.io%2Fdraft-ietf-opsawg-pcap%2Fdraft-ietf-opsawg-pcaplinktype.txt
might be a better diff. I will post -03 now.
Let me paste in here the Designated Expert advice.
What do you think about sentence two? We aren't telling them not to accept
specifications that are hard to get at, but rather to maybe push a bit for
something more accessible.
# Guidance for Designated Experts
When processing a request for a Specification Required allocation the
Designated Experts are expected to be able to find the relevant specification
at a clearly stable URL.
It is noted that many enterprise web sites do not maintain URLs over a long
period of time, and a documented in a "wp-uploaded" section is highly likely to
disappear.
In addition Specifications that require a reader to click through any kind of
marketing or legal agreement are not considered public.
(This is the opinion of other corporate lawyers, who worry about what their
employees might have agreed to)
The specification needs to be clearly written, and when the contents of the
link type can contain an IPv4 or IPv6 header, then the octets between the
beginning of the link type and the IP header needs to be very clearly specified
in that document.
Specifications which are not publically available, but which may be obtained
via liason agreements (such as to ITU-T, 3GPP, IEEE, etc.) are acceptable
particularly if the document will be public eventually, but are discouraged.
For other documents, the Designated Expert will need use their judgement, or
consult the WG or an Area Director.
Linktypes may be allocated for specifications not publically available may be
made within the First-Come/First-Served area.
This includes specifications that might be classified.
The minimal requirement is for a contact person for that link type.
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
