On Feb 27, 2014, at 6:04 PM, Tony Finch <d...@dotat.at> wrote: > L. Aaron Kaplan <kap...@cert.at> wrote: > >> I agree. You probably meant >> >> ws = *( >> %x20 | ; Space >> %x09 ; Horizontal tab >> ) > > Er yes, typo :-) > >>> How are sensor_id octet strings encoded as JSON strings? >> >> Correct. > > I need a bit more clarification than that :-) All right then :)
> Section 3.5.1 of the -01 > version of your draft says that a sensor_id is an opaque octet string, > which cannot safely be encoded as a JSON string because JSON strings have > to be valid UTF-8. > Okay, quite a nice catch. I would not have noticed that. Since I am the only user of the sensor_id field right now, I'd say we remove the text: "The sensor_id is an opaque byte string as defined by RFC 5001 in section 2.3 [RFC5001]. The sensor_id MUST be escaped as defined in section 2.6 of RFC4627 [RFC4627]." and just leave: "This field returns the sensor information where the record was seen. This field is represented as a JSON [RFC4627] string." Would that be OK for you? > Tony. > -- > f.anthony.n.finch <d...@dotat.at> http://dotat.at/ > Plymouth, Biscay, FitzRoy: West, veering northwest, 7 to severe gale 9, > perhaps storm 10 later. Very rough or high, occasionally very high. Rain or > showers. Moderate, occasionally poor. --- // L. Aaron Kaplan <kap...@cert.at> - T: +43 1 5056416 78 // CERT Austria - http://www.cert.at/ // Eine Initiative der nic.at GmbH - http://www.nic.at/ // Firmenbuchnummer 172568b, LG Salzburg
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
