Eric was making was the pedantic point that the Javascript 'standard' is
called ECMAScript and that is what the spec should reference.


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> Behalf Of Dave Crocker
> Sent: Saturday, February 11, 2006 7:29 PM
> To: Digital Identity Exchange
> Subject: [dix] use of non-ietf work in ietf standards
> 
> 
> 
> > dumb clients but given that Javascript isn't any kind of IETF 
> > standard--it's hard to see how we could require it in an IETF 
> > standard.
> 
> 
> small procedural point:  the ietf does it all the time.
> 
> x.400 interoperability specs. IP-over-* specs. Anything using Unicode.
> 
> And so on.
> 
> (The subject line of this message is changed so that no one 
> confuses this note with a comment on dix or your substantive 
> review of it.)
> 
> d/
> -- 
> 
> Dave Crocker
> Brandenburg InternetWorking
> <http://bbiw.net>
> 
> _______________________________________________
> dix mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/dix
> 
> 

_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix

Reply via email to