Re: [Dime] New Liaison Statement, "LS to IETF for clarification on RFC 4006 for Diameter Base Protocol"

Jouni Korhonen <> Thu, 05 May 2016 17:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32CEE12D7E9 for <>; Thu, 5 May 2016 10:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0UR9qtijWufz for <>; Thu, 5 May 2016 10:43:16 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4E04E12D7E3 for <>; Thu, 5 May 2016 10:42:52 -0700 (PDT)
Received: by with SMTP id r5so39260047pag.1 for <>; Thu, 05 May 2016 10:42:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=i+REI8bnYvfh8IGADq+4L5ZHR+p6veMaBtmXl2JnpAM=; b=F9RSKh8DU+PSoHGTtUr7Ht9k/1A/P9IlWxbWrbEL1tmOAwS968F14H5UVsKgsUGMoH e9s5lEXqAZFTy8dbl0UWjvczPxC8xV4Ei3s+IujaW+NHyOWspCEc5iDK59Yjgu+LQT7o ylZsQPsFHCVn6Kxmt2UwHITtlMpDbm81jSR0TA9I7x2i/mWXDlZ4j804H1c5whEqINIp x4Zi7d0XD4FkQiOimO6K6yDIsZNVwDmDg0jyCY2sueCZt5NjI4kjURXYSkYoRwtFevim VfL3ylfpy2FRReT1by9QrRKXGIBcsztvWXFdAmfIcAM9Ukoith10u/LhJFik+iMGgawV VVWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=i+REI8bnYvfh8IGADq+4L5ZHR+p6veMaBtmXl2JnpAM=; b=erm8JHkC/l5AbbRj+yP/hyBEH/1Xw3DkFCS1UICjj/A2XFB0C940N6QUymPOav25OA Ihnk130dUH2VLtI6WwKtbqs9yM9tW/aMLFjuSyaDqjyOXCVkUDOu8DWedki35St69X28 5m3XjvWoc7Y05yzywjDQjpjPjCa7M/TFRHBlVEoIO1YUP3Px8AV6/hSjkcaYZDFWnsoj +etBzhWrgmy8Ms6f0uvs+QK9r56cpRPti48OaXQ0kXssfgVtFbOT2qF62IMMYxv53lHG vRewvKP/HYpOZqMeQqG8mgZI6vVguQTcBgvVaLi7uIihnfMoP2Ov3H738WwnzsrkbTA/ DoYQ==
X-Gm-Message-State: AOPr4FWAOyu1x84oCzo2r5rqqlVRilb86vt4MHNJAZUQLBwnwMlg/Z996tX8gge7PpOWOw==
X-Received: by with SMTP id tp10mr22550670pab.159.1462470171872; Thu, 05 May 2016 10:42:51 -0700 (PDT)
Received: from ?IPv6:2601:647:4205:17e0:f182:ba5f:6ca2:c10? ([2601:647:4205:17e0:f182:ba5f:6ca2:c10]) by with ESMTPSA id ve11sm15198688pab.21.2016. (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 May 2016 10:42:51 -0700 (PDT)
References: <>
To: "" <>
From: Jouni Korhonen <>
Message-ID: <>
Date: Thu, 05 May 2016 10:42:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Cc: Joel Jaeggli <>,
Subject: Re: [Dime] New Liaison Statement, "LS to IETF for clarification on RFC 4006 for Diameter Base Protocol"
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 May 2016 17:43:23 -0000


Have a look at the LS we recently received from the 3GPP SA5. Looking at 
our charter and what we have discussed recently updating RFC4006 is not 
likely.. unless someone volunteers to take a ball on it asap.

I have not read RFC4006 for a long time so my memory might serve me 
wrong. The immediate things to look into when responding to this LS 
(assuming we would only give recommendations) relate to security. 
RFC4006 AVPs seems to care about the AVL 'P' bit setting and 'Encr'. 
Since both of these are deprecated in RFC6733 we better say something 
about that.

Another thing, which is outside the LS scope, though, is the CCA CCF. 
Here I am referring to the discussion in Buenos Aires on the answer 
message when 'E' bit is set.

Any thoughts? We have about a week to prepare the reply LS. The due date 
is 23rd May.

- Jouni

5/4/2016, 5:04 PM, Liaison Statement Management Tool kirjoitti:
> Title: LS to IETF for clarification on RFC 4006 for Diameter Base Protocol
> Submission Date: 2016-05-04
> URL of the IETF Web page:
> Please reply by 2016-05-23
> From: "Maryse Gardella" <>
> To: Jouni Korhonen <>,Lionel Morand <>
> Cc: Benoit Claise <>,Lionel Morand <>,Joel Jaeggli <>,Jouni Korhonen <>,Diameter Maintenance and Extensions Discussion List <>,
> Response Contacts:
> Technical Contacts:
> Purpose: For action
> Body:
> Attachments:
>      LS to IETF for clarification on RFC 4006 for Diameter Base Protocol