Re: [radext] Extended Identifiers: is manual configuration in scope?

Hi, Stefan:

Yes, it is, and such a config is allowed in the following section of
draft-chen-radext-identifier-attr-02.txt. 

----
2.2. Status-Server Considerations

   Unless specified by configuration, a client MUST NOT send a RADIUS
   packet (other than the Status-Server request) with the "Extended
   Identifier Attribute" to a server until it has received a response
   from the server confirming its support for the Extended Identifier
   feature using the "Extended Identifier Attribute".

Thanks.  -- Enke

On 12/14/17 6:43 AM, Stefan Winter wrote:
> Hello,
> 
> 
> there is one question to which the answer did not become entirely clear
> in the discussion so far.
> 
> 
> Could the authors of the respective drafts please clearly indicate the
> answer to this question:
> 
> 
> Is a manually configured mode of operation considered in scope?
> 
> 
> I.e. do you consider it a valid use case that an implementation presents
> administrators with a configuration option "Enable Extended
> Identifiers", and that the implementation starts making use of that
> feature /without/ a capability negotiation using Status-Server with its
> next-hop peer?
> 
> 
> Greetings,
> 
> 
> Stefan Winter
> 
> 
> 
> 
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext
> 