I don't think this is an issue worth objecting to.
Complexity exists at many levels. There is complexity of specification and
complexity of implementation. The two are not the same.
I can imagine two reasons why I might want to have ASN.1 in XML. The first is
that I want to use a single set of
Eric Rescorla has agreed to deal with the third party disclosure on my
behalf.
thanks for all the volunteers of help.
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Folks, it should be surprising to no one here that we've recieved the
following disclosure; it is a direct result of my mail yesterday. I'd
ask the community to evaluate this potential IPR in addition to the
disclosure from Redphone.
---BeginMessage---
Dear Russ Housley, Mark Brown:
An IPR
On 2/27/07, McDonald, Ira [EMAIL PROTECTED] wrote:
Yes - from the IEEE/ISTO Printer Working Group, see the
Job Monitoring MIB (RFC 2707) which defined the textual
convention 'JmNaturalLanguageTagTC'
Ah, silly me, I forgot that I hadn't written the part that populates
the database with TCs yet.
Hi -
From: Hallam-Baker, Phillip [EMAIL PROTECTED]
To: Harald Tveit Alvestrand [EMAIL PROTECTED]; Fred Baker [EMAIL
PROTECTED]
Cc: ietf@ietf.org
Sent: Tuesday, February 27, 2007 6:45 AM
Subject: RE: Protest: Complexity running rampant
...
DER would not have been so bad if they had chosen
The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document:
- 'Reasons to Move NAT-PT to Historic Status '
draft-ietf-v6ops-natpt-to-historic-00.txt as an Informational RFC
This document recommends that the IESG reclassifies RFC 2766 from
Standards
I am pleased to announce that the 2006-2007 NomCom selection and
confirmation process for IESG and IAOC is complete. At this time, on
behalf of the NomCom, here is the list of IESG and IAOC members selected
for the positions under review by the NomCom:
IESG
Russ HousleyIETF
