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

RE: Review of draft-ietf-radext-status-server-05 (Part II)

To: "'Alan DeKok'" <aland@deployingradius.com>, "'Ignacio Goyret'" <i.goyret@alcatel-lucent.com>
Subject: RE: Review of draft-ietf-radext-status-server-05 (Part II)
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
Date: Wed, 24 Feb 2010 14:27:07 -0800
Cc: <radiusext@ops.ietf.org>
In-reply-to: <4B85A2D5.2020906@deployingradius.com>
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl> <4B7AB10C.5030800@deployingradius.com> <201002242136.o1OLaSc0017148@cliff.eng.ascend.com> <4B85A2D5.2020906@deployingradius.com>

Alan said:

"  I could see this being useful for checking "liveliness" of upstream
realms.  But some providers have dozens, if not hundreds of realms, and
this functionality gets awkward pretty quickly."

[BA] Since Status-Server isn't forwardable, I'm not sure how it could help
with the realm reachability issue.  


--
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/>

Follow-Ups:
- Re: Review of draft-ietf-radext-status-server-05 (Part II)
  - From: Alan DeKok <aland@deployingradius.com>

References:
- Review of draft-ietf-radext-status-server-05 (Part II)
  - From: Bernard Aboba <bernard_aboba@hotmail.com>
- Re: Review of draft-ietf-radext-status-server-05 (Part II)
  - From: Alan DeKok <aland@deployingradius.com>
- Re: Review of draft-ietf-radext-status-server-05 (Part II)
  - From: Alan DeKok <aland@deployingradius.com>

Prev by Date: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Next by Date: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Previous by thread: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Next by thread: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Index(es):
- Date
- Thread