the node MUST do a DNS SRV query using a Service name of
"p2psip_enroll" and a protocol of tcp to find an enrollment server
and form the URL by appending a path of "/p2psip/ enroll" to the
overlay name.
I guess, the space after "/p2psip/ " is a typo (?)
Regards
David A. Bryan schrieb:
Definitely the right place. We don't currently have an implementation
specific list (something like the sip-implementors list), but even if
we did, what you are noticing is a bug in the spec proposal, and the
right place for that is always the working group. Thanks for all the
comments.
David (as chair)
On Thu, Feb 18, 2010 at 2:39 PM, neil.young <[email protected]> wrote:
The XML does also not validate correctly against
http://www.hitsw.com/xml_utilites/
Just one question: Is this the right place to discuss those kind of problems
or is there another group, more focused on implementations?
Kind regards
Neil.Young schrieb:
Additional information:
If I remove all elements, tagged with "chord:" and "ext:" from the XML
everything is fine. But I believe this is not the intention.
Regards
neil.young schrieb:
10.1:
I'm unable to generate a proxy class from the XML. Normaly I'm using xsd.exe
to convert plain xml to an xsd, if the xsd isn't provided. The schema then
is converted to proxy class, which might easily be used in C# code. This
works with several XML based information contents in 3GPP projects, but not
with RELOAD.
Furthermore the XML is syntactically incorrect in the line containing
"<turn-density> 10 </turn-density><"
The final "<" has to be removed.
I was taking this xml and fed it to xsd.xml
c:\xsd reload.xml
The resulting 3 xsd files (reload.xsd, reload_app1.xsd, reload_app2.xsd)
could not be converted to a wrapper class by
c:\xsd reload.xsd /language:cs /classes
The error is:
Schema validation warning:
urn:ietf:params:xml:ns:p2p:config-ext1:example-extention-Element not
declared. Line 18, position 16.
Schema validation warning:
urn:ietf:params:xml:ns:p2p:config-chord:chord-ping-interval-Element not
declared. Line 19, position 16.
Schema validation warning:
urn:ietf:params:xml:ns:p2p:config-chord:chord-update-interval-Element not
declared Line 20, position 16.
Schema validation warning: Das
urn:ietf:params:xml:ns:p2p:config-ext1:example-kind-extention-Element not
declared. Line 56, position 34.
Although this is just warnings, the code generation fails too in the first
step:
Error: Error generating classes for schema 'reload'.
- 'urn:ietf:params:xml:ns:p2p:config-ext1:example-extention' missing.
Regards
neil.young schrieb:
5.3.1.1
<quote>
Thus, the 3-byte value
"Foo" would be encoded as: 03 46 4f 4f.
</quote>
In fact it should be "encoded" as "03 46 6f 6f", or it should be named "FOO"
:) (BTW: Those kind of errors in your draft is on the level I'm able to
discover... :))
Question behind: May I assume, that every "opaque" value, as far as no
explicitly determined in length, is preceded by a length byte (or more bits)
on the wire?
Regards
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
