[Softwires] Opsdir telechat review of draft-ietf-softwire-map-radius-22

Al Morton via Datatracker <noreply@ietf.org> Sat, 04 May 2019 15:34 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: softwires@ietf.org, ietf@ietf.org, draft-ietf-softwire-map-radius.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Al Morton <acmorton@att.com>
Message-ID: <155698407561.18637.7880253981474877056@ietfa.amsl.com>
Date: Sat, 04 May 2019 08:34:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/hqHbgidfhQ01rpQNBNABf47nFBg>
Subject: [Softwires] Opsdir telechat review of draft-ietf-softwire-map-radius-22

Reviewer: Al Morton
Review result: Ready

The time-line of this draft suggests that these extension are worth a try as -is.
This is a seven-year (and counting) development. The review of a Radius expert has been
included (and this is not among my qualifications).  There was one trial implementation, 
as noted in the shepherd's form (but it's not clear that there will be additional attention
to this beyond the approval process). The Doc Shepherd has done a nits-check, etc.

[Softwires] Opsdir telechat review of draft-ietf-… Al Morton via Datatracker