So it looks like you went with not having the type flag in the
bootstrap node option, but I also don't see anything in the
configuration listing the security mechanism.

How does a peer know which security mechanism is being used (i.e., how
does one indicate a mechanism other than TLS, and thus a non-TLS
connection?) I expected to see either the flag or something lower in
the XML indicating what security protocol the network used.

It might have missed something somewhere that specifies how to do it.
If so, can you explain how to do a system that chooses to use another
mechanism? We can't just ignore this -- many folks on the list have
raised several reasons for TLS to me mandatory to imp but allow other
security mechanisms. We need to be able to do that somehow in the
bootstrap file.

Thanks,

David (as individual)

On Mon, Mar 8, 2010 at 8:02 PM, Bruce Lowekamp <[email protected]> wrote:
> An -08 revision of the base draft has been posted.  This draft
> primarily addresses more of the WGLC feedback and subsequent feedback
> on the mailing list.  We have again updated
> http://svn.resiprocate.org/rep/ietf-drafts/p2psip/wglc1-comments.txt
> with responses to specific email.  In particular, the new revisions
> reflect the discussion on list about the xml configuration document,
> etc.
>
> To address WGLC feedback, there is a very rough proposal for a DRR
> option header in Section 5.3.2.4, which essentially proposes allowed
> an option header that encodes an AttachReqAns for DRR purposes.  We
> believe the proposal (fully speced out) is sufficient to provide DRR
> functionality in the protocol, although further extensions would be
> required to determine when it is safe to use, etc, if someone desires
> to use it in any case where it is not known to work (i.e. public
> servers).  As indicated in the text, this is a proposal that we would
> like list and f2f discussion of before proceeding further.
>
> Bruce
> _______________________________________________
> P2PSIP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/p2psip
>
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip

Reply via email to