Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based Redirection In Diameter) to Proposed Standard

Hi,

One additional late comment:

The Redirect-Realm AVP is proposed as new standard AVP. The document provides the following description:

3.3. The Redirect-Realm AVP

   The Redirect-Realm AVP (code TBD2) is of type DiameterIdentity.  It
   specifies a realm to which a node receiving a redirect indication
   containing the result code value DIAMETER_REALM_REDIRECT_INDICATION
   and the Redirect-Realm AVP SHOULD route the original request.  The M
   flag for the Redirect-Realm AVP MUST be set, and the V flag MUST NOT
   be set.

The last sentence is not needed and should be removed.
First, the RFC6733 clarifies that:

      The 'M' bit MUST be set according to the rules defined in the
      application specification that introduces or reuses this AVP.
      Within a given application, the M-bit setting for an AVP is
      defined either for all command types or for each command type.

So the normative text "MUST be set" is incorrect in this specification: the setting of the M-bit will be specified in the application using this new AVP.

The normative statement on the V-bit is not required. The setting of the V-bit only indicates that the AVP code value belongs to the address space identified by the Vendor-Id. So per se, it is not strictly forbidden to set the V-bit but if set, this code will no longer designate a standard AVP :)

Therefore the proposed change is the following:

OLD:

3.3. The Redirect-Realm AVP

   The Redirect-Realm AVP (code TBD2) is of type DiameterIdentity.  It
   specifies a realm to which a node receiving a redirect indication
   containing the result code value DIAMETER_REALM_REDIRECT_INDICATION
   and the Redirect-Realm AVP SHOULD route the original request.  The M
   flag for the Redirect-Realm AVP MUST be set, and the V flag MUST NOT
   be set.

NEW:

3.3. The Redirect-Realm AVP

   The Redirect-Realm AVP (code TBD2) is of type DiameterIdentity.  It
   specifies a realm to which a node receiving a redirect indication
   containing the result code value DIAMETER_REALM_REDIRECT_INDICATION
   and the Redirect-Realm AVP SHOULD route the original request.

Regards,

Lionel

-----Message d'origine-----
De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part de The IESG
Envoyé : mardi 13 août 2013 18:24
À : IETF-Announce
Cc : dime@ietf.org
Objet : [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based Redirection In Diameter) to Proposed Standard

The IESG has received a request from the Diameter Maintenance and
Extensions WG (dime) to consider the following document:
- 'Realm-Based Redirection In Diameter'
  <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-08-27. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   Message redirection is a basic capability provided by the Diameter
   base protocol.  In its conventional form, message redirection is
   performed by an application-independent "redirect agent", which
   returns one or more individual hosts to the message sender as
   possible destinations of the redirected message.

   However, in some circumstances an operator may wish to redirect
   messages to an alternate domain without specifying individual hosts.
   This document specifies an application-specific mechanism by which
   that can be achieved.  New applications may incorporate this
   capability by reference to the present document.

   Because the redirection mechanism is application-specific, it must be
   performed by a Diameter server or proxy rather than a basic redirect
   agent as defined in the Diameter base protocol.  A new term, "Realm-
   based Redirect Server", is introduced in this document to
   differentiate the application-specific nature of realm-based
   redirection from the conventional Diameter redirection performed by a
   basic redirect agent.

   This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to
   the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
   AVPs.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/ballot/

The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1254/

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.