[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Pending Errata for RADEXT

To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Pending Errata for RADEXT
From: Alan DeKok <aland@deployingradius.com>
Date: Mon, 26 Oct 2009 16:49:28 -0400
Cc: "dromasca@avaya.com" <dromasca@avaya.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
In-reply-to: <BLU137-W25E5D871347FF170E5028793BA0@phx.gbl>
References: <BLU137-W25E5D871347FF170E5028793BA0@phx.gbl>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)

Bernard Aboba wrote:
> The following errata relate to problems with RFC 4282 which were
> uncovered in the IDNAbis effort.  While the nature of the problems is
> pointed out in the IDNAbis documents which have just completed IETF last
> call, the solutions will require substantial revisions to RFC 4282 which
> can only be accomplished in a -bis document.  Therefore these errata
> should probably either be classified as "pending update" or rejected:
> 
> 1848, 1849, 1850

  I would suggest "pending update".

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

References:
- Re: Pending Errata for RADEXT
  - From: Bernard Aboba <bernard_aboba@hotmail.com>

Prev by Date: Re: [Technical Errata Reported] RFC3162 (1923)
Next by Date: Re: [Technical Errata Reported] RFC3162 (1923)
Previous by thread: RE: Pending Errata for RADEXT
Index(es):
- Date
- Thread