btns at ietf66

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>>>>> "strand" == strand 
<Love> writes:
    >> "Discuss API issues". - I think
that's me as well.
    -> defining the scope is the most important part.

    strand> And part of that is figure out how to
interact with other
    strand> working groups that also have ideas on how to
control IPsec
    strand> to use in their protocols.

  At this point, I think that the shim6 people still did not
comprehend
that the shim6/btns API intersect is empty. 
  I guess I can do a venn diagram.

  I think that the shim6/hip intersect is non-empty, and
that the
hip/btns intersect is also non-empty, but I don't know if:
	 hip - shim6 is != 0
and	 hip - btns  is != 0

  I.e. if btns and shim6 APIs can provide everything that
HIP needs.

  My instinct is that this is a IRTF todo.

- -- 
]       ON HUMILITY: to err is human. To moo, bovine.       
   |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON
   |net architect[
] mcrxelerance.com      http://www.san
delman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel
hacking, security guy"); [

    "The Microsoft _Get the Facts CD_ does not work on
Linux." - orospakr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Finger me for keys

iQEVAwUBRKMV4oCLcPvd0N1lAQLvrwf9HdhGzMWhFctf7HRxfqVC3RJMQn9x
a3+7
RMPEo66TVY6ahhrPhGvNIJCP45lpLz2YNXhBQlIuRF+JusbNpKJ1eZaucSRt
ds3V
9W9PNSxjHZa5Yk0P2R1XAYGASea6pmTdivONEM3/I7fK1p49WHf9ILLWtA3C
r2Qb
e6QFPWQZppAMJXib/svJAjRdng90EVObp0l0mIYMBlQsOfAvgKutNWdqBZ5p
Xcpc
RwR1HRCDWAzHoCAfcBSrLWnBnt05Jq+WiVs4BHmbMDml3/lh0EC9g5Fy9OLz
bG3l
UpKRlxUkzhQc1aJj+BiZ+PYGGS+dVB6ktk8CfKyNFZ76opzx8H37Sw==
=sggu
-----END PGP SIGNATURE-----
_______________________________________________