[radext] Basic question about user-name attribute

Fadi Bushnaq <zardoss@gmail.com> Sat, 10 November 2018 10:36 UTC

Return-Path: <zardoss@gmail.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B413712F18C for <radext@ietfa.amsl.com>; Sat, 10 Nov 2018 02:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNSsdIwgFXvH for <radext@ietfa.amsl.com>; Sat, 10 Nov 2018 02:36:37 -0800 (PST)
Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CB89127332 for <radext@ietf.org>; Sat, 10 Nov 2018 02:36:37 -0800 (PST)
Received: by mail-it1-x12d.google.com with SMTP id t189-v6so6490701itf.1 for <radext@ietf.org>; Sat, 10 Nov 2018 02:36:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=iaUgPQsmxgeOaDbZXLfUXuG6605DCVmIKGdHqV1l7cM=; b=XP2l0OK6t/WCiYhodyIa2o6MvkY6C5oTdvPtvDCl3WXpflcLfAt4uWk5nHhWe3mZJ4 IUkYTdflXucUX6GF67UzYnIUdiWFmXIlFTxvrHZ5SZyuecBYyw4AZE6+Ro+M/Wek2TRx jGgEBCBgnTx/f62JeRAUTIJz/0PvlDksCDid40hfT+JQdeLsVOiobG0ha0+5yp5FwOU6 IeJLWFGEy7OkDYLlI4MvV58//Sixew1iONovWKFYUeshOsRCnc5abjKUKbXA5BPnFR62 QTarSAFuuNzSGAj8Yzx1eb0gf7GHfnO69JcraTH3Qy93CQKKQx7rYll5feWGScsfQ9ZT 5iAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=iaUgPQsmxgeOaDbZXLfUXuG6605DCVmIKGdHqV1l7cM=; b=iusgzew8oRjOKlET2mA0xUb2VzzNdo/nPaKzfxtZbFgIIY52hFY441A9q6xjkWAqyx D2ksOOX10cp8KxEfR/8fNgEsR8JU+PbxsbwmcjMyRQjZTzEkTIA3Bz0k1jQQjY+QqgUc /rDcw6D1gn1/MV03rfKbESVZ9W6Gcm5oJQj1jPnZNvH/mS2+nVd/s82zFIUH1DpLiahV 0y251w3Glg9HOo/TiGM+R3o4ONfNvCisCQ6/HOqMpFX3HHXP2Ah9xK9gDP+oMZsmHx9/ 81T48W8/NaXQ9yaCrq2Tzbax8k84nGqPGdERQzCkPw7YnNMnjDavCWm4r7skr1+G2msa uhSA==
X-Gm-Message-State: AGRZ1gJ7ot62ozt32D+xy8JhUvzo4ZGky8OQ4u6WRnPYE2mr8f6T0u42 Jwokc7BarqEb8wujjlrsz8V5QiIQc+QdRIPEj5WC0iPD
X-Google-Smtp-Source: AJdET5fI/DVjATze4agWQgeGoOImuJ9zcokPw0AMYjG3K6LRkcH0spq+yfYaf/iTA/lRDCDy5lSwtjg1vb5fPqVhR1o=
X-Received: by 2002:a02:8522:: with SMTP id g31-v6mr10624538jai.68.1541846196392; Sat, 10 Nov 2018 02:36:36 -0800 (PST)
MIME-Version: 1.0
From: Fadi Bushnaq <zardoss@gmail.com>
Date: Sat, 10 Nov 2018 11:36:19 +0100
Message-ID: <CALSGxMPXsNXWOS8V+GHVg7h-QR0NausRczdHV_T-bDUu-TKukA@mail.gmail.com>
To: radext@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d599e2057a4d0a22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/mPg2c5PV_XBIQ3_JLBbozhlTCls>
Subject: [radext] Basic question about user-name attribute
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2018 11:36:32 -0000

I hope this is the right place to post such questions

>From RFC 2865 section 5.1, user-name MUST be sent in access-request packets
and MAY be sent in access-accept.

The question is, in case it is decided to include this attribute in the
access-accept packet, does it have to be identical to the value received in
the access-request relative to the same session or can it be different?

Any reference to where this is documented would be highly appreciated.

Thanks.
Fadi