Re: [sip-clf] Using the PEN
Gonzalo Salgueiro <gsalguei@cisco.com> Mon, 28 March 2011 17:45 UTC
Return-Path: <gsalguei@cisco.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A1433A6A5E for <sip-clf@core3.amsl.com>; Mon, 28 Mar 2011 10:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.386
X-Spam-Level:
X-Spam-Status: No, score=-10.386 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3n1B4DSGAGH6 for <sip-clf@core3.amsl.com>; Mon, 28 Mar 2011 10:45:36 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 7CCEA3A68A9 for <sip-clf@ietf.org>; Mon, 28 Mar 2011 10:45:36 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2SHlD0h026127 for <sip-clf@ietf.org>; Mon, 28 Mar 2011 13:47:13 -0400 (EDT)
Received: from rtp-gsalguei-8719.cisco.com (rtp-gsalguei-8719.cisco.com [10.116.61.58]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2SHlCnT027344; Mon, 28 Mar 2011 13:47:12 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-42-904684587"
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <Pine.GSO.4.63.1103261921470.11931@sjc-cde-013.cisco.com>
Date: Mon, 28 Mar 2011 13:47:11 -0400
Message-Id: <DC7B9328-74FF-4DE3-8143-B0E2E760668C@cisco.com>
References: <Pine.GSO.4.63.1103261921470.11931@sjc-cde-013.cisco.com>
To: Chris Lonvick <clonvick@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] Using the PEN
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 17:45:37 -0000
Fantastic! Thanks Chris. We'll proceed with my proposal and be very clear as to the treatment of PEN, including PEN=0, with respect to the logging of optional fields. Thanks again. --Gonzalo On Mar 28, 2011, at 1:38 PM, Chris Lonvick wrote: > Hi, > > I ran the question of using PEN=0 and PEN=<vendor id> past a few people. > > IANA did not have an opinion. > > David Harrington, the author of RFC5612 thinks that it would be good. > http://www.rfc-editor.org/rfc/rfc5612.txt > > The best response I got was from Dan Romascanu who wrote: >>> PENs are using in various protocols and the usage of Enterprise Numbers >>> may (at least in theory) be different from protocol to protocol, so it >>> would be best if the respective protocol documents refer explicitly how >>> 'special' values like 0 are used. True, the convention that 0 is the >>> value reserved for IETF standards is widely used (for example to >>> identify standard notifications in SMI) but as SIP-CLF defines a >>> different DML I would suggest that adopting the convention is OK, and >>> mentioning it explicitly is best. > > Bert Wijnen agreed with Dan. > > Thanks, > Chris > > _______________________________________________ > sip-clf mailing list > sip-clf@ietf.org > https://www.ietf.org/mailman/listinfo/sip-clf
- [sip-clf] Using the PEN Chris Lonvick
- Re: [sip-clf] Using the PEN Gonzalo Salgueiro