--On 29. mars 2007 11:50 -0500 Mark Brown [EMAIL PROTECTED] wrote:
Simon,
I filed for patent (Jan and Sep 2005) and later promoted TLS authz (Feb
2006) in good faith. It is possible that the patent claims can be read
more broadly than I expected, but that's a fairly detailed and unresolved
On 4 apr 2007, at 00.45, Mark Brown wrote:
Harald,
I want to apologize again for screwing up the IPR disclosure process.
Normal IPR disclosure process is to alert the IETF community via
the IETF
website that a patent has been filed. I mistakenly thought that
adding the
boilerplate IPR
Dan == Dan Harkins [EMAIL PROTECTED] writes:
Dan Sam,
Dan I guess the question is, what text in this I-D would
Dan prevent a new key distribution protocol based on AAA in which
Dan the authentication server sent a copy of the peer's keys
Dan willy-nilly to every
Thanks Mark - this makes it clear that we need to work on our information
materials, to make it clear to people what the requirement is.
BTW, RFC 3979 doesn't make a difference between published and unpublished
applications - both require a disclosure. Section 6.4.1 describes how to
refer to
The IESG has approved the following documents:
- 'The Message Session Relay Protocol '
draft-ietf-simple-message-sessions-19.txt as a Proposed Standard
- 'Relay Extensions for the Message Sessions Relay Protocol (MSRP) '
draft-ietf-simple-msrp-relays-10.txt as a Proposed Standard
These
The IESG has approved the following document:
- 'Softwire Problem Statement '
draft-ietf-softwire-problem-statement-03.txt as an Informational RFC
This document is the product of the Softwires Working Group.
The IESG contact persons are Mark Townsley and Jari Arkko.
A URL of this
The IESG has approved the following document:
- 'IS-IS Extensions for Advertising Router Information '
draft-ietf-isis-caps-07.txt as a Proposed Standard
This document is the product of the IS-IS for IP Internets Working Group.
The IESG contact persons are Bill Fenner and Ross Callon.
A
