Re: [Roll] Ticket #10: Closed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Roll] Ticket #10: Closed
Hi Michael,
> -----Original Message-----
> From: roll-bounces at ietf.org [mailto:roll-bounces at ietf.org] On
> Behalf Of Michael Richardson
> Sent: lundi 9 novembre 2009 15:43
> To: roll WG
> Subject: Re: [Roll] Ticket #10: Closed
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> >>>>> "Julien" == Julien Abeille <(jabeille)"
> <jabeille at cisco.com>> writes:
> Julien> Just game boys would all support the same OCP. Game boy +
> Julien> PSP may indeed not support the same one. For me this is
> Julien> interop, and does not happen by magic. People that want
> Julien> their device to interoperate have to check they implement
> Julien> the same things. Otherwise IETF ends up mandating that all
> Julien> device implement the same OCP, same instance, as
> well as the
> Julien> same transport, the same application layer protocol, the
> Julien> same application, same security, the same data
> Julien> structures....
>
> Yes, that's certainly true. It is a good, not a bad.
>
> And if done correctly, interop does happen by magic.
> You are reading this email, because email was standardized.
Well I am reading this email because I have a laptop that supports a
bunch of RFCs, and bunch of email standards.
So I guess we disagree on benefits vs costs. And again if the root does
not send OCP0, the game boy having OCP0 is useless. Are we trying to
solve an adhoc network problem? Do the requirements drafts and RFCs
require this kind of scenario?
Best,
Julien
> It did not need to be standardized for technical discussion
> seperately from being standardized for use with close relatives.
>
> The precise profile of what is MUST, and what is MAY, is
> sometimes delegated to other documents, but the base
> specification should not have dozens of options if we expect
> to get anywhere.
>
> >> How do I form a network of game boys is my question.
>
> You have to use OCP0. We have to specify that.
> The document will likely want to say SHOULD for it.
>
> - --
> ] He who is tired of Weird Al is tired of life!
> | firewalls [
> ] Michael Richardson, Sandelman Software Works, Ottawa, ON
> |net architect[
> ] mcr at sandelman.ottawa.on.ca
> http://www.sandelman.ottawa.on.ca/ |device driver[
> Kyoto Plus: watch the video
> <http://www.youtube.com/watch?v=kzx1ycLXQSE>
> then sign the petition.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Finger me for keys
>
> iQEVAwUBSvgqVYCLcPvd0N1lAQL9xgf7BR/WMiVbwCZTwMBfRC66LSNEcMac4WfM
> LzBCkupWl7HCiyf9oJ0kOIqUaYbTIK5tRItEuaW1LiqKEZksWr4Gxsel3EyTgodL
> aMwbzoBmxheUdmvQiqMTJnoIYB9A2uZfAb2D36z8JLjWV/IGy9Ijze7sVdExe1s2
> 1Yl5ZHGKbPwcYOU5meAWaLNmVjPNTNjd+mtyS1SGUkEYTWgDK4ydCdJ9anqd2gfF
> 5M0Vkr2zgaYVbn0l6t6Ni3KC6eQ0wcoSP9hB8LaT26lEx3Vo/Hr/eucbR8QoGhxb
> g/wS1kxTVO9pINjMklEeD5sGg0lRnztsl8MCBN0D8wtF4VkLGS6xuw==
> =aI9Q
> -----END PGP SIGNATURE-----
> _______________________________________________
> Roll mailing list
> Roll at ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.