<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Michael Richardson skrev 2014-08-01
07:01:<br>
</div>
<blockquote cite="mid:13627.1406869303@sandelman.ca" type="cite">
<pre wrap="">
Additional sources of IANA per-enterprise namespace:
1) Radius extensions
2) DHCP extensions
I am not in favour of this.
IANA Considerations has enough easy to pass processes to get numbers, no
specification required.
Enterprises/governments that are super paranoid about having their deeds
recorded in registries do what they have always done: get TRW to register for
them.
</pre>
</blockquote>
I'm sorry I don't quite get your objection, are you saying that we
shouldn't define a vendor block type? <br>
But rather have an IANA block type registry and any one can just
register a block type?<br>
<br>
Come to think of it perhaps we shouldn't allow block types without a
specification. If it is pcap-ng then<br>
it should be specified what the content is otherwise people can
define their own file formats.<br>
Regards<br>
Anders<br>
<blockquote cite="mid:13627.1406869303@sandelman.ca" type="cite">
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pcap-ng-format mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pcap-ng-format@winpcap.org">pcap-ng-format@winpcap.org</a>
<a class="moz-txt-link-freetext" href="https://www.winpcap.org/mailman/listinfo/pcap-ng-format">https://www.winpcap.org/mailman/listinfo/pcap-ng-format</a></pre>
</blockquote>
<br>
</body>
</html>