![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Fred Baker wrote:is it a bad thing to provide
the expressive nature of ASN.1 in a human-readable and popular data representation?
The one thing IETF standardization certainly ought to imply is that there is a real constituency interesting in using the specification in the near-term.
Who wants to use this spec, now, and why?
I almost sent an email asking this question when I read the drafts. My reaction was "This seems like a lot of stuff to put on the standards track without being the output of a WG."
I didn't, because I figured there must be some significant constituency that wants this standardized. So, is there or not?
d/
Andy
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.