
From nobody Wed Nov  4 22:15:37 2015
Return-Path: <amorris@amsl.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9617D1ACD3B for <opsawg@ietfa.amsl.com>; Wed,  4 Nov 2015 22:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rrrp8evdnAqZ for <opsawg@ietfa.amsl.com>; Wed,  4 Nov 2015 22:15:34 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 43B121A00F0 for <opsawg@ietf.org>; Wed,  4 Nov 2015 22:15:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 228C41E59F2 for <opsawg@ietf.org>; Wed,  4 Nov 2015 22:14:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJFoEohwuZRt for <opsawg@ietf.org>; Wed,  4 Nov 2015 22:14:52 -0800 (PST)
Received: from dhcp-28-33.meeting.ietf94.jp (dhcp-28-33.meeting.ietf94.jp [133.93.28.33]) by c8a.amsl.com (Postfix) with ESMTPA id C9D7C1E59F1 for <opsawg@ietf.org>; Wed,  4 Nov 2015 22:14:51 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Wed, 4 Nov 2015 22:15:34 -0800
Message-Id: <69B95AD2-3A3F-4153-9E35-28D4417B9BAF@amsl.com>
To: opsawg@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Sendlaterdate: Wed, 4 Nov 2015 22:15:34 -0800
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/my_zOaHT0FJoR2DUfWHU7ckFFcs>
Subject: [OPSAWG] Queue for opsarea Remote Attendees
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 06:15:35 -0000

If you are planning to participate in the opsarea session here at IETF =
94 today =97 either locally in Yokohama or as a remote participant =97 =
we want to make sure that you are aware that the IETF is providing =
remote participants with a fairly new way to ask questions or make =
comments. In addition to using the Jabber room, for the opsarea session =
there is also the opportunity for remote participants to enter a virtual =
queue and ask questions directly into the meeting room.=20

This experimental queue was used in several sessions at IETF 92 and IETF =
93, so you may have already seen it in action. There will be two queues =
for the opsarea session =97 a virtual queue and an actual (in-room) =
queue. Remote attendees will log into the Meetecho platform and will =
have a virtual mic line that they can enter if they have a question or =
comment. In-room participants will continue to use normal mic lines.=20

Instructions for remote participants are at =
http://ietf94.conf.meetecho.com/index.php/Remote_Participation.=20

Information on how to join the Meetecho session is at =
http://ietf94.conf.meetecho.com/.

Verify that you are WebRTC compliant (required to use the virtual queue) =
by performing a self-test here: =
http://ietf94.conf.meetecho.com/index.php/Self_Test.=20

Regards,
Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From nobody Thu Nov  5 17:09:58 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 601191A8BB2; Thu,  5 Nov 2015 17:09:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 j---do4IpjJw; Thu,  5 Nov 2015 17:09:54 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A4D81A8AAA; Thu,  5 Nov 2015 17:09:54 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2C0BgA3Q8ZV/yYyC4dbGQGCNCEsVGoFqW4Gg0qPQioJggSFeQKBJjgUAQEBAQEBAYEKhCUBAQMSG0wSAQwJFVYmAQQBDQ0MDogMAQysaaA6AQEBAQEFAQEBAQEBHIYfigoxgx+BFAWVCwGFAYlwhmqRBBEGD4N9gjeBBAEBAQ
X-IPAS-Result: A2C0BgA3Q8ZV/yYyC4dbGQGCNCEsVGoFqW4Gg0qPQioJggSFeQKBJjgUAQEBAQEBAYEKhCUBAQMSG0wSAQwJFVYmAQQBDQ0MDogMAQysaaA6AQEBAQEFAQEBAQEBHIYfigoxgx+BFAWVCwGFAYlwhmqRBBEGD4N9gjeBBAEBAQ
X-IronPort-AV: E=Sophos;i="5.15,634,1432612800";  d="scan'208,217";a="150070018"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 05 Nov 2015 20:09:53 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 05 Nov 2015 20:09:52 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Fri, 6 Nov 2015 02:09:51 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "opsec@ietf.org" <opsec@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: SACM Vulnerability assessment scenario
Thread-Index: AdEYL9WBvXS9CXrQRpiQvzpjTMwSWQ==
Date: Fri, 6 Nov 2015 01:09:50 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BE85BAA@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA6BE85BAAAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/5W2RXgu2q-MofzU7oV1l4w11ReU>
Cc: "Haynes, Dan" <dhaynes@mitre.org>, Adam Montville <adam.w.montville@gmail.com>
Subject: [OPSAWG] SACM Vulnerability assessment scenario
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 01:09:56 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA6BE85BAAAZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Following my short info in the OPSAWG/OPSAREA meeting yesterday - the I-D t=
hat I was mentioning is http://datatracker.ietf.org/doc/draft-coffin-sacm-v=
uln-scenario/. It describes the vulnerability assessment scenario and the c=
oncept of vulnerability reports which the SACM WG is considering as useful =
to baseline requirements and use as a reference use case for the work in th=
e current (first) phase of the SACM work.

We would appreciate one or even more review from the OPSEC and OPSAWG commu=
nity. We are interested especially whether the use case and process describ=
ed in this I-D fits the way vulnerability assessment and reports are being =
seen by operators in their daily activities.

Thanks and Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA6BE85BAAAZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Following my short info in the OPSAWG/OPSAREA meetin=
g yesterday &#8211; the I-D that I was mentioning is
<a href=3D"http://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/=
">http://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/</a>. It =
describes the vulnerability assessment scenario and the concept of vulnerab=
ility reports which the SACM WG is
 considering as useful to baseline requirements and use as a reference use =
case for the work in the current (first) phase of the SACM work.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We would appreciate one or even more review from the=
 OPSEC and OPSAWG community. We are interested especially whether the use c=
ase and process described in this I-D fits the way vulnerability assessment=
 and reports are being seen by operators
 in their daily activities. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA6BE85BAAAZFFEXMB04globa_--


From nobody Tue Nov 10 17:05:30 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4D0D1ACE5A for <opsawg@ietfa.amsl.com>; Tue, 10 Nov 2015 17:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 opc6lkEuKo-Q for <opsawg@ietfa.amsl.com>; Tue, 10 Nov 2015 17:05:27 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00AF41ACE5B for <opsawg@ietf.org>; Tue, 10 Nov 2015 17:05:26 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id E4F32200A5; Tue, 10 Nov 2015 20:09:22 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id C310E637F8; Tue, 10 Nov 2015 20:05:25 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A57C8637F3; Tue, 10 Nov 2015 20:05:25 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: opsawg@ietf.org, Pcap-ng file format <pcap-ng-format@winpcap.org>
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 10 Nov 2015 20:05:25 -0500
Message-ID: <28578.1447203925@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/yJ7LczDObabWAH4SrmJ886bqMVg>
Cc: dominique barthel <dominique.barthel@orange-ftgroup.com>, tcpdump-workers <tcpdump-workers@lists.tcpdump.org>
Subject: [OPSAWG] comments/edits on pcapng
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 01:05:29 -0000

--=-=-=
Content-Type: text/plain


11hr trips home are good for document review...
Is the XML around? Found it: https://github.com/pcapng/pcapng/pull/38

I reviewed draft-tuexen-opsawg-pcapng, while it hasn't had an -01, some work
has been occuring in the github copy, and so the effort isn't dead, just not
as visible.

For those that don't know, I'm been the packager/maintainer for tcpdump and
libpcap for about the last 15 years, and until 5-6 years ago, pretty much
anyone that used *pcap* format, used libpcap to read/write it.
That has changed (which is good!) since the advent of the pcapng format.
I personally didn't have a lot of time to review the ideas when they were in
their formative stage.  Aside from my initial whine, I think the document is
quite mature, and I'd like to see it move forward, either within opsawg, or
as ISE.

Tcpdump has been able to read pcapng files for awhile now, but still writes
pcap format files.

This is definitely not my first read of the document, but the idea of going
via OPSAWG surfaced at IETF90 (Toronto), but seems to have gotten stuck?

In general, I had thought that pcapng was going to start with an identical
magic as pcap, but that the "version_major" would say, "2", i.e:
pcap1:	bpf_u_int32 magic = 0xa1b2c3d4  (mutated for byte order)
	u_short version_major;
	u_short version_minor;

when in fact, pcapng files start with:
     int32_t type = 0x0A0D0D0A
     int32_t length;
     int32_t byte_order_magic;
     int16_t major; int16_t minor;

and the initial block isn't any different than any other blocks.  I see the
logic for this, and I don't have a problem with this on account of working,
deployed code, I just wish they could all have been "pcap" files.  So this is
more a whine than a comment.

I also find "pcapng" a poor long-term name, mostly it's the "ng" part that I
dislike. .pc2p or something might have been better.

section 4.1 says this about major/minor:

        Major Version: number of the current mayor version of the
              format. Current value is 1. This value should change if the format changes in
              such a way that code that reads the new format could not read the old format
              (i.e., code to read both formats would have to check the version number and
              use different code paths for the two formats) and code that reads the old
              format could not read the new format.

        Minor Version: number of the current minor version of the
              format. Current value is 0. This value should change if the format
              changes in such a way that code that reads the new format could read
              the old format without checking the version number but code that
              reads the old format could not read all files in the new format.

and I think that I don't buy it.
[First, "major version" should have been started at "2" :-) ]

But, more importantly, we have an easily, and almost always incremenally
extendable file format.  It's hard to imagine a change so drastic that it
would be worth incrementing the major version number that would still leave
enough of the file format intact that there would be any value left.
One would also wind up changing magic/header numbers.
With protocols that are online, it is different, as there can be a bit of
negotiation when major numbers don't match, but not really the case for files
resting on disk.

So I think that we should simply turn this into a 4-byte int32 field.  Let's
just put the highest *RFC* number that must be understood in order to comprehend
all the blocks present.  At approx. 3500 RFCs/10 years, 32-bits will last a
long long long time... We could even do this with just the Minor Version and
be good until rfc65535, which might be by oh year 2265 assuming the IETF
continues at it's present rate.
Maybe we could have a bit at the top which says, "There are experimental
blocks, and understanding them is critical to the semantic content of file"

On the Interface Description Block, (section: 4.2), the table shown should be
an IANA controlled registry.  The reference to section 3.5 is initially
confusing when reading.  I think that there should be a single table (in
section 3.5).  I see that the Section Header Block also reuses codes used in
the IDB:  I think that this is a mistake, the codes in a comment block should
not be context dependant.   My pull request takes care of all of them, I
hope.  I numbered them sequentially, but we could leave gaps.

We will need a registration formula for this registry, and I think that
First-Come / First Served (RFC5226/BCP26, section 4.1) will do fine for this one.

On the subject of the Encryption Block.  In discussion on the list many asked
if we needed it.  Let me suggest that we do, but that yes, we need more
information in it.  First, we need to make it look more like ESP (RFC4303):


+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ----
|               Security Parameters Index (SPI)                 | ^Int.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Cov-
|                      Sequence Number                          | |ered
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ----
|                    Payload Data* (variable)                   | |   ^
~                                                               ~ |   |
|                                                               | |Conf.
+               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Cov-
|               |     Padding (0-255 bytes)                     | |ered*
+-+-+-+-+-+-+-+-+               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |   |
|                               |  Pad Length   | Next Header   | v   v
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ------
|         Integrity Check Value-ICV   (variable)                |
~                                                               ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


But, we don't need a SeqNumber, or a Next Header.  We can probably assume
that the things inside are already padded to 32-bit boundary, but
self-describing padding is easy and simple.  Yes, we should have an ICV.
I make the SPI 64-bits to give it more space.  Who can decrypt and
even with what algorithm is actually unimportant/private.  If you have
to ask, then it's not you!  Further a comment in the SHR would permit
proper document management, if the file was part of an evidence locker.


+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         Security Parameters Index (SPI -- 64 bits)            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    Payload Data* (variable)                   |
~                                                               ~
|                                                               |
+               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               |     Padding (0-255 bytes)                     |
+-+-+-+-+-+-+-+-+                             +-+-+-+-+-+-+-+-+-+
|                                             |    Pad Length   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         Integrity Check Value-ICV   (variable)                |
~                                                               ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Now, about LinkType: I suggest that having libpcap/tcpdump continue to
maintain the table is not ideal.  Instead, let's create an IANA registry for
it, populate it with existing values, and make the libpcap group the Expert
Review.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVkKUUoCLcPvd0N1lAQK3Qwf/Y/9G6Q+4igyteXE+MN4qc2OtZV1o0JhZ
0RcUcaZC/F1IaS/hhTTTqS46BIb+QZk40oqbDsr9BafCS9UBliPH710VWUSQkJEE
4s0Dm6El9Igd7qGHCPybkrbuhkxo3c4/w2UR0wXtNjaSDP/SW+sbiZHUPokz4ykE
IZUJaohAUIx3X57YoiumuOyPfAtvtxU5uz9gEPymVAB6LCItQsci5iSWd9FkFY8s
7IKK45qmXHbzXKyOHUcT9MrfwLPvIg604tRgYpi4iqpkzPCuRuR20zL160S9XcJZ
SlQI6Q3z4PD5YKVxYq3JnLE1vxVXGtunhBRYCCQKP29JXCq3pItgYA==
=C9Fg
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Nov 10 19:24:49 2015
Return-Path: <guy@alum.mit.edu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D9E61A8AB7 for <opsawg@ietfa.amsl.com>; Tue, 10 Nov 2015 19:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no
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 Cf6PbnS34Vpx for <opsawg@ietfa.amsl.com>; Tue, 10 Nov 2015 19:24:46 -0800 (PST)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 723BB1A8AA0 for <opsawg@ietf.org>; Tue, 10 Nov 2015 19:24:46 -0800 (PST)
Received: from [192.168.42.66] (173-228-4-166.dsl.dynamic.fusionbroadband.com [173.228.4.166]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tAB3OgG0004567 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 10 Nov 2015 19:24:43 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Guy Harris <guy@alum.mit.edu>
In-Reply-To: <28578.1447203925@sandelman.ca>
Date: Tue, 10 Nov 2015 19:24:42 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E942894B-FDD3-41D3-8DAA-BFBDADB56EEE@alum.mit.edu>
References: <28578.1447203925@sandelman.ca>
To: Pcap-ng file format <pcap-ng-format@winpcap.org>
X-Mailer: Apple Mail (2.2104)
X-Sonic-CAuth: UmFuZG9tSVYTzRWHd3XZiwoN3aILqBCWJzxFcF3gUDrNYS0bcrgYDRG3p4uejuZpaOxofymuOkrcHbIs2iHXRwbXIIPjVyp8
X-Sonic-ID: C;NpvRvyOI5RGCqL0U9jFv0A== M;oDlVwCOI5RGCqL0U9jFv0A==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/wep3bSEH4sIlpKORSvPbLhH4wdI>
Cc: opsawg@ietf.org, tcpdump-workers <tcpdump-workers@lists.tcpdump.org>, dominique barthel <dominique.barthel@orange-ftgroup.com>
Subject: Re: [OPSAWG] [pcap-ng-format] comments/edits on pcapng
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 03:24:48 -0000

On Nov 10, 2015, at 5:05 PM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:

> I reviewed draft-tuexen-opsawg-pcapng, while it hasn't had an -01, =
some work
> has been occuring in the github copy, and so the effort isn't dead, =
just not
> as visible.

The official version of the spec is, indeed =
draft-tuexen-opsawg-pcapng.xml at the GitHub repository.

> Tcpdump has been able to read pcapng files for awhile now, but still =
writes
> pcap format files.

...as is the case with other programs using libpcap.

The current capabilities are what can be done without any additions to =
the API.  At some point I plan to add additional APIs to expose the full =
capabilities of pcapng when reading captures and to write pcapng files.  =
The APIs for reading files will also support pcap files, so if a program =
such as tcpdump is changed to use the new APIs when available, it'll =
still handle pcap files.

> section 4.1 says this about major/minor:
>=20
>        Major Version: number of the current mayor version of the
>              format. Current value is 1. This value should change if =
the format changes in
>              such a way that code that reads the new format could not =
read the old format
>              (i.e., code to read both formats would have to check the =
version number and
>              use different code paths for the two formats) and code =
that reads the old
>              format could not read the new format.
>=20
>        Minor Version: number of the current minor version of the
>              format. Current value is 0. This value should change if =
the format
>              changes in such a way that code that reads the new format =
could read
>              the old format without checking the version number but =
code that
>              reads the old format could not read all files in the new =
format.
>=20
> and I think that I don't buy it.
> [First, "major version" should have been started at "2" :-) ]
>=20
> But, more importantly, we have an easily, and almost always =
incremenally
> extendable file format.  It's hard to imagine a change so drastic that =
it
> would be worth incrementing the major version number that would still =
leave

> enough of the file format intact that there would be any value left.

Well, one change that would be that drastic would be changing it from a =
format in which each block type has its own name space for options to a =
format in which there's a single global name space for options, and thus =
changing the option numbers.  That change would not only mean that old =
code would no longer be able to read the new files, it would also mean =
that code that handles the new files would need a different code path to =
handle the old files.

It would not, however, change the format of the blocks, for example, so =
the rest of the code, with the exception of the option processing code, =
would need no change (and the option processing code would only need to =
handle the renumbering of the options).

> One would also wind up changing magic/header numbers.

The main magic number is the byte-order magic number, which would only =
need to change if the format of the SHB changed.

> So I think that we should simply turn this into a 4-byte int32 field.  =
Let's
> just put the highest *RFC* number that must be understood in order to =
comprehend
> all the blocks present.  At approx. 3500 RFCs/10 years, 32-bits will =
last a
> long long long time... We could even do this with just the Minor =
Version and
> be good until rfc65535, which might be by oh year 2265 assuming the =
IETF
> continues at it's present rate.

So are you suggesting that updates to the format, such as the addition =
of new blocks, new options, new link-layer types, etc. would be done =
with RFCs?

That would fit with the use of IANA registries for block types/option =
values/link-layer header types/etc..

> On the Interface Description Block, (section: 4.2), the table shown =
should be
> an IANA controlled registry.

I.e., replace http://www.tcpdump.org/linktypes.html with an IANA =
registry?

> The reference to section 3.5 is initially
> confusing when reading.  I think that there should be a single table =
(in
> section 3.5).  I see that the Section Header Block also reuses codes =
used in
> the IDB:  I think that this is a mistake, the codes in a comment block =
should
> not be context dependant.  My pull request takes care of all of them, =
I
> hope.

Does your pull request also bump the current major version number?  =
Renumbering the options means that all the code out there that reads the =
current file formats won't be able to read the new format *and* code =
that *does* read the new format would need to interpret the option =
values differently based on the version number, so that sure sounds like =
a major version change.

I don't see what the problem is with different block types having =
different option name spaces.  Common code to handle options in all =
block types wouldn't be that useful - that code wouldn't, for example, =
be able to do anything useful with the interface speed option in a Name =
Resolution Block.  (And what do you mean by a "comment block"; we don't =
have blocks whose sole purpose is to contain comments, we have a comment =
option that can be used in any block, the content of which is solely =
intended for display to humans.)

> On the subject of the Encryption Block.  In discussion on the list =
many asked
> if we needed it.  Let me suggest that we do, but that yes, we need =
more
> information in it.

Well, the first question is what sort of information would be put in it. =
 The current spec just says it "is used to store encrypted data" and =
says of the data in it that "Once decrypted, it originates other =
blocks.", but it doesn't say what sort of stuff is being encrypted!  =
Lists of credit card numbers? :-)

> Now, about LinkType: I suggest that having libpcap/tcpdump continue to
> maintain the table is not ideal.  Instead, let's create an IANA =
registry for
> it, populate it with existing values, and make the libpcap group the =
Expert
> Review.

So where would the actual formats be made available?

If we look at, for example, the snoop data link types registry:

	=
http://www.iana.org/assignments/snoop-datalink-types/snoop-datalink-types.=
xhtml#snoop-datalink-types-2

it just gives the code, a name for the type, and a reference, which =
links to RFCs as a reference.

If we were to publish an RFC for each linktype, or possibly incorporate =
a number of linktypes in a single RFC so as not to waste an entire RFC =
to say "IEEE 802.3 Ethernet" for type 1, that would work - in effect

	=
http://www.iana.org/assignments/pcap-datalink-types/pcap-datalink-types.xh=
tml

would replace the "LINKTYPE_ value" and a somewhat more human-oriented =
version of the "LINKTYPE_ name" column, and point to RFCs that provide =
information now in the "Description" column, of =
http://www.tcpdump.org/linktypes.html.

I don't think an RFC is required as a reference, so we wouldn't have to =
wait for an RFC to percolate through the process before making a new =
link-layer header type available, but that would leave open the question =
of what to use as a reference until the RFC comes out, and if you don't =
want www.tcpdump.org to store the description until it shows up in an =
RFC...

...well, actually I guess we could use the pcap-ng GitHub repository for =
that.=


From nobody Wed Nov 11 07:49:17 2015
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E06531B2AAE for <opsawg@ietfa.amsl.com>; Wed, 11 Nov 2015 07:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=no
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 zHECEpA9VHQ7 for <opsawg@ietfa.amsl.com>; Wed, 11 Nov 2015 07:49:14 -0800 (PST)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (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 BA5D91B2AAD for <opsawg@ietf.org>; Wed, 11 Nov 2015 07:49:13 -0800 (PST)
Received: by ykba77 with SMTP id a77so54597954ykb.2 for <opsawg@ietf.org>; Wed, 11 Nov 2015 07:49:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari_net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uKYGYiTXAo+chLIcSRBqwvPSGzyM8Xc4lb1+ESrNQjU=; b=CRSptmFMEp4NLK75ytI6HEqiJI9APDv69bCJ/Ehmt9NeM8U9RNdety6NJYp1WNxW9T mlcyFyq/X4l2AeBZgXR6sl9X7CtqnMgrjFBa6KP8NSsuU9Ow8Odxs3pZuGSk6sYkmqJF 3aSxIzxgw0AwwHNp3slI269NRcMRijJM4JD0UHKm/jB2ZaVzo0gytBfGwWULp44x7OEo ZvrLy2KeVZ5NIsa8ymf0VptwBfLc2bHnBrzH73MMoj0gxBxXaOUmGLFNDYQzqYfaKM9g 2f+Chibbr+0DxDfipPRZmhBZ7Uw14RXI4Efee/7ttnYcNRNO2sY0UkPWaNSyyBAOWEso +c7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uKYGYiTXAo+chLIcSRBqwvPSGzyM8Xc4lb1+ESrNQjU=; b=hCDqPN/d8XTGb/eD7sX0mlkp6D4kjrRdzmpfgu+b4YuKGPd4Q3TNNokTGOYqTCq6q7 FRfmpjWsHnSh7niS5+fGBdB9VVQGyriKYnainpY3fQrrI65hPtj6+gQhjCLf/jFCvtwk B5Nkop6G1Y6RTmI3rIqW4EU/134X36oAf9CIEyQPAW7gA+77esVshPKaaJboS8+8aopg GhZ4su64uXTvHeRuZnNgyUtApHc21uFAnRkYoJc3oaIVsqKRzkvEsiF1bZyWlI0iVSyA VaHNdcNux0OGW+noijBsUyZqE0EC4aZs2qu9189GMsdwIMixFZh8L8Kg15VYmIXmQ7+7 y2dw==
X-Gm-Message-State: ALoCoQnH8lsi+oY2v4BkgbEEtQuVPIDDtelGe0h6m08nhKPCAlleCwvjxJ1vV872nNztLJIFPRg4
MIME-Version: 1.0
X-Received: by 10.13.205.70 with SMTP id p67mr11206924ywd.249.1447256559888; Wed, 11 Nov 2015 07:42:39 -0800 (PST)
Received: by 10.37.202.11 with HTTP; Wed, 11 Nov 2015 07:42:39 -0800 (PST)
In-Reply-To: <28578.1447203925@sandelman.ca>
References: <28578.1447203925@sandelman.ca>
Date: Thu, 12 Nov 2015 00:42:39 +0900
Message-ID: <CAHw9_iLeqt-Eui=hOxcfribvgk3OXUQNXjUdTvrvCq09weYXZg@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/rb2AdFMkHddh3stO0jJrSRmanLE>
Cc: Pcap-ng file format <pcap-ng-format@winpcap.org>, "opsawg@ietf.org" <opsawg@ietf.org>, tcpdump-workers <tcpdump-workers@lists.tcpdump.org>, dominique barthel <dominique.barthel@orange-ftgroup.com>
Subject: Re: [OPSAWG] comments/edits on pcapng
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 15:49:16 -0000

On Wed, Nov 11, 2015 at 10:05 AM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
>
> 11hr trips home are good for document review...
> Is the XML around? Found it: https://github.com/pcapng/pcapng/pull/38
>
> I reviewed draft-tuexen-opsawg-pcapng, while it hasn't had an -01, some work
> has been occuring in the github copy, and so the effort isn't dead, just not
> as visible.

I'm glad to hear this - it seemed like something worth pursuing - I
had a todo that got buried under other things to followup with the
authors to see whatever happened.

>
> For those that don't know, I'm been the packager/maintainer for tcpdump and
> libpcap for about the last 15 years, and until 5-6 years ago, pretty much
> anyone that used *pcap* format, used libpcap to read/write it.
> That has changed (which is good!) since the advent of the pcapng format.
> I personally didn't have a lot of time to review the ideas when they were in
> their formative stage.  Aside from my initial whine, I think the document is
> quite mature, and I'd like to see it move forward, either within opsawg, or
> as ISE.

The IETF is traditionally not very good at formats and such, but I'm
game to try progress it under OpsAWG.
W

>
> Tcpdump has been able to read pcapng files for awhile now, but still writes
> pcap format files.
>
> This is definitely not my first read of the document, but the idea of going
> via OPSAWG surfaced at IETF90 (Toronto), but seems to have gotten stuck?
>
> In general, I had thought that pcapng was going to start with an identical
> magic as pcap, but that the "version_major" would say, "2", i.e:
> pcap1:  bpf_u_int32 magic = 0xa1b2c3d4  (mutated for byte order)
>         u_short version_major;
>         u_short version_minor;
>
> when in fact, pcapng files start with:
>      int32_t type = 0x0A0D0D0A
>      int32_t length;
>      int32_t byte_order_magic;
>      int16_t major; int16_t minor;
>
> and the initial block isn't any different than any other blocks.  I see the
> logic for this, and I don't have a problem with this on account of working,
> deployed code, I just wish they could all have been "pcap" files.  So this is
> more a whine than a comment.
>
> I also find "pcapng" a poor long-term name, mostly it's the "ng" part that I
> dislike. .pc2p or something might have been better.
>
> section 4.1 says this about major/minor:
>
>         Major Version: number of the current mayor version of the
>               format. Current value is 1. This value should change if the format changes in
>               such a way that code that reads the new format could not read the old format
>               (i.e., code to read both formats would have to check the version number and
>               use different code paths for the two formats) and code that reads the old
>               format could not read the new format.
>
>         Minor Version: number of the current minor version of the
>               format. Current value is 0. This value should change if the format
>               changes in such a way that code that reads the new format could read
>               the old format without checking the version number but code that
>               reads the old format could not read all files in the new format.
>
> and I think that I don't buy it.
> [First, "major version" should have been started at "2" :-) ]
>
> But, more importantly, we have an easily, and almost always incremenally
> extendable file format.  It's hard to imagine a change so drastic that it
> would be worth incrementing the major version number that would still leave
> enough of the file format intact that there would be any value left.
> One would also wind up changing magic/header numbers.
> With protocols that are online, it is different, as there can be a bit of
> negotiation when major numbers don't match, but not really the case for files
> resting on disk.
>
> So I think that we should simply turn this into a 4-byte int32 field.  Let's
> just put the highest *RFC* number that must be understood in order to comprehend
> all the blocks present.  At approx. 3500 RFCs/10 years, 32-bits will last a
> long long long time... We could even do this with just the Minor Version and
> be good until rfc65535, which might be by oh year 2265 assuming the IETF
> continues at it's present rate.
> Maybe we could have a bit at the top which says, "There are experimental
> blocks, and understanding them is critical to the semantic content of file"
>
> On the Interface Description Block, (section: 4.2), the table shown should be
> an IANA controlled registry.  The reference to section 3.5 is initially
> confusing when reading.  I think that there should be a single table (in
> section 3.5).  I see that the Section Header Block also reuses codes used in
> the IDB:  I think that this is a mistake, the codes in a comment block should
> not be context dependant.   My pull request takes care of all of them, I
> hope.  I numbered them sequentially, but we could leave gaps.
>
> We will need a registration formula for this registry, and I think that
> First-Come / First Served (RFC5226/BCP26, section 4.1) will do fine for this one.
>
> On the subject of the Encryption Block.  In discussion on the list many asked
> if we needed it.  Let me suggest that we do, but that yes, we need more
> information in it.  First, we need to make it look more like ESP (RFC4303):
>
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ----
> |               Security Parameters Index (SPI)                 | ^Int.
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Cov-
> |                      Sequence Number                          | |ered
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ----
> |                    Payload Data* (variable)                   | |   ^
> ~                                                               ~ |   |
> |                                                               | |Conf.
> +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Cov-
> |               |     Padding (0-255 bytes)                     | |ered*
> +-+-+-+-+-+-+-+-+               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |   |
> |                               |  Pad Length   | Next Header   | v   v
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ------
> |         Integrity Check Value-ICV   (variable)                |
> ~                                                               ~
> |                                                               |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> But, we don't need a SeqNumber, or a Next Header.  We can probably assume
> that the things inside are already padded to 32-bit boundary, but
> self-describing padding is easy and simple.  Yes, we should have an ICV.
> I make the SPI 64-bits to give it more space.  Who can decrypt and
> even with what algorithm is actually unimportant/private.  If you have
> to ask, then it's not you!  Further a comment in the SHR would permit
> proper document management, if the file was part of an evidence locker.
>
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |         Security Parameters Index (SPI -- 64 bits)            |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |                    Payload Data* (variable)                   |
> ~                                                               ~
> |                                                               |
> +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |               |     Padding (0-255 bytes)                     |
> +-+-+-+-+-+-+-+-+                             +-+-+-+-+-+-+-+-+-+
> |                                             |    Pad Length   |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |         Integrity Check Value-ICV   (variable)                |
> ~                                                               ~
> |                                                               |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> Now, about LinkType: I suggest that having libpcap/tcpdump continue to
> maintain the table is not ideal.  Instead, let's create an IANA registry for
> it, populate it with existing values, and make the libpcap group the Expert
> Review.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Thu Nov 12 08:26:41 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF251B2B09 for <opsawg@ietfa.amsl.com>; Thu, 12 Nov 2015 08:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 le5f5GGbwPAM for <opsawg@ietfa.amsl.com>; Thu, 12 Nov 2015 08:26:37 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A95681B2AC1 for <opsawg@ietf.org>; Thu, 12 Nov 2015 08:26:37 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B1B4E203AE; Thu, 12 Nov 2015 11:30:39 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id DB2A9637F8; Thu, 12 Nov 2015 11:26:36 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C6FE2637F3; Thu, 12 Nov 2015 11:26:36 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Guy Harris <guy@alum.mit.edu>
In-Reply-To: <E942894B-FDD3-41D3-8DAA-BFBDADB56EEE@alum.mit.edu>
References: <28578.1447203925@sandelman.ca> <E942894B-FDD3-41D3-8DAA-BFBDADB56EEE@alum.mit.edu>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 12 Nov 2015 11:26:36 -0500
Message-ID: <29455.1447345596@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/2cb6K0IcQG8dMY-lngVqYgIo528>
Cc: Pcap-ng file format <pcap-ng-format@winpcap.org>, opsawg@ietf.org, dominique barthel <dominique.barthel@orange-ftgroup.com>, tcpdump-workers <tcpdump-workers@lists.tcpdump.org>
Subject: Re: [OPSAWG] [tcpdump-workers] [pcap-ng-format] comments/edits on pcapng
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 16:26:40 -0000

--=-=-=
Content-Type: text/plain


Guy Harris <guy@alum.mit.edu> wrote:
    > Well, one change that would be that drastic would be changing it from a
    > format in which each block type has its own name space for options to a
    > format in which there's a single global name space for options, and
    > thus changing the option numbers.  That change would not only mean that
    > old code would no longer be able to read the new files, it would also
    > mean that code that handles the new files would need a different code
    > path to handle the old files.

Well, I don't feel too strongly about changing this.
I would suggest that we could leave values < 256 as "local", and provide new
numbers which were globally unique as aliases.  But that still leaves code
that is needed to read old files which likely never goes away, and so what's
the point.

    >> So I think that we should simply turn this into a 4-byte int32 field.
    >> Let's just put the highest *RFC* number that must be understood in
    >> order to comprehend all the blocks present.  At approx. 3500 RFCs/10
    >> years, 32-bits will last a long long long time... We could even do
    >> this with just the Minor Version and be good until rfc65535, which
    >> might be by oh year 2265 assuming the IETF continues at it's present
    >> rate.

    > So are you suggesting that updates to the format, such as the addition
    > of new blocks, new options, new link-layer types, etc. would be done
    > with RFCs?

To the extent that they would be "standards", yes.
If someone wants to allocate a block type for their own use, that would be
fine, it would just be RFCXXXX + extension.

    > That would fit with the use of IANA registries for block types/option
    > values/link-layer header types/etc..

    >> On the Interface Description Block, (section: 4.2), the table shown
    >> should be an IANA controlled registry.

    > I.e., replace http://www.tcpdump.org/linktypes.html with an IANA
    > registry?

Yes, I think that this is reasonable.

    >> The reference to section 3.5 is initially confusing when reading.  I
    >> think that there should be a single table (in section 3.5).  I see
    >> that the Section Header Block also reuses codes used in the IDB: I
    >> think that this is a mistake, the codes in a comment block should not
    >> be context dependant.  My pull request takes care of all of them, I
    >> hope.

    > Does your pull request also bump the current major version number?

Fair point, it should do that too if we were to accept this change.

    > I don't see what the problem is with different block types having
    > different option name spaces.  Common code to handle options in all
    > block types wouldn't be that useful - that code wouldn't, for example,
    > be able to do anything useful with the interface speed option in a Name
    > Resolution Block.  (And what do you mean by a "comment block"; we don't
    > have blocks whose sole purpose is to contain comments, we have a
    > comment option that can be used in any block, the content of which is
    > solely intended for display to humans.)

Perhaps I've mis-understood how these suboptions work.

    >> On the subject of the Encryption Block.  In discussion on the list
    >> many asked if we needed it.  Let me suggest that we do, but that yes,
    >> we need more information in it.

    > Well, the first question is what sort of information would be put in
    > it.  The current spec just says it "is used to store encrypted data"
    > and says of the data in it that "Once decrypted, it originates other
    > blocks.", but it doesn't say what sort of stuff is being encrypted!
    > Lists of credit card numbers? :-)

I think that essentially, it encrypts other blocks, such as captures, etc.

    >> Now, about LinkType: I suggest that having libpcap/tcpdump continue to
    >> maintain the table is not ideal.  Instead, let's create an IANA
    >> registry for it, populate it with existing values, and make the
    >> libpcap group the Expert Review.

    > So where would the actual formats be made available?

We'd have to include a few key ones into this document, and the rest would
continue to have the rather loose references that the web site has now.

    > I don't think an RFC is required as a reference, so we wouldn't have to
    > wait for an RFC to percolate through the process before making a new
    > link-layer header type available, but that would leave open the
    > question of what to use as a reference until the RFC comes out, and if
    > you don't want www.tcpdump.org to store the description until it shows
    > up in an RFC...

So, what happens right now is that we do Expert Review.  People ask us for a
link type, and we beat on them a bit to give a slightly stable document to
point at, or at least to argue why no existing type works for them.
Then they get the number, and if we are lucky, we also have a stable link to
their format.  With IANA Expert Review, we could essentially do exactly the
same thing --- just that IANA would write down the result.

Numbers can be assigned by RFC as well, and can be assigned early, and IANA
is happy to change the reference from draft-foo-bar to RFCxyaz as the
document progresses.
But, it can also just be a link to http://www.company.com/technote/foo.html,
or it can, as it says now, say, "Used by Company XYZ for Proprietary FOO"

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVkS9uYCLcPvd0N1lAQKNjAf/QlivjuRCFb5V2YgWZ75/m4lT9jxtrOEM
Dcw0MblrL2UzglIhZ2+GanrNGJSZ90OLLkxrGUrJGCgFEitQfH3eLZZKvS4wfwdz
+sW1pGeQH4XbjQdggroqzsJgzacY0UZJN5EErL5gvm/cLcqKIH2Kc6S+3SfHH65P
7R9FTDzV3DqOCC9TvQeadlPYLqZDUdGs6htSU6AmbKCHAfWGcb1P8SHu1yCxabY/
M9Z0a1kfnBtVzBkLX2qkyrd7Daz3TtPhRaIr9xjyBLhw7AUapzftjY2fi2tE506e
kBO/6bxAm256Ze4oUgAtOnVBbtbuGt9Ofl+cv2kPQk1QjstLcSDYRQ==
=fHkT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Nov 12 08:31:58 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1901B2FF6 for <opsawg@ietfa.amsl.com>; Thu, 12 Nov 2015 08:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0e1ZBbOdE93o for <opsawg@ietfa.amsl.com>; Thu, 12 Nov 2015 08:31:55 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF4021B2FF5 for <opsawg@ietf.org>; Thu, 12 Nov 2015 08:31:55 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D02DF2015D; Thu, 12 Nov 2015 11:35:57 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 07906637F8; Thu, 12 Nov 2015 11:31:54 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E244D637F3; Thu, 12 Nov 2015 11:31:54 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAHw9_iLeqt-Eui=hOxcfribvgk3OXUQNXjUdTvrvCq09weYXZg@mail.gmail.com>
References: <28578.1447203925@sandelman.ca> <CAHw9_iLeqt-Eui=hOxcfribvgk3OXUQNXjUdTvrvCq09weYXZg@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 12 Nov 2015 11:31:54 -0500
Message-ID: <30541.1447345914@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/SbaEAA7ut7H_1AyMIba2DXtMPF4>
Cc: Pcap-ng file format <pcap-ng-format@winpcap.org>, "opsawg@ietf.org" <opsawg@ietf.org>, tcpdump-workers <tcpdump-workers@lists.tcpdump.org>, dominique barthel <dominique.barthel@orange-ftgroup.com>
Subject: Re: [OPSAWG] comments/edits on pcapng
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 16:31:57 -0000

--=-=-=
Content-Type: text/plain


Warren Kumari <warren@kumari.net> wrote:
    > The IETF is traditionally not very good at formats and such, but I'm
    > game to try progress it under OpsAWG.  W

On Sunday at the ETSI 6lo plugfest Dominique Barthel described to me a way
that the IOT-Lab is using *pcap* (with custom LINKTYPE_USR0...) in a
syslog/MILE/INCH-like way, except that they are debug events rather than
security events.  Interspersed with packets that were actually captured and
caused the debug... viewable in wireshark.

PCAP files already travel over TCP and SSH connections between collectors and
analyzers... so it's not just a format at rest anymore.

I am not subscribed to the opsawg list, I'm sure.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVkS+94CLcPvd0N1lAQKqVAf/fwsJ+goV6yyx1LX4NdsdHEckoDQuUZTS
NQWdNd9fSmGGUrklhmH5aJpZgfZxz/6mBdYkV5UcBMKoWrEO4yXk7YrE8gPSOWc+
r3Dn4xauoRXlDL1qC7At6rZSMP3WTUXIb/yxHvK5MiGKgDay4mG2XPiy7hfWjOCh
QjBlQVYofhE51lXO/uEmaZeK/RiW7hJPkZy6BUzdPiOXAKnW7xRCLCxChZvTET8F
wqEOMWn2mcq7uvEmcqGj/K4aouLgQz97F+8eIH4ZSPPvxndSTs34IBlNUHC9gP4F
KkAHOAWyWU0rmZY30kIlNgIU66EtBKAkDJRYlB82zXXKgBaXsMD0tQ==
=nFC+
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Nov 13 10:37:06 2015
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A65E81B2ABD for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 10:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=no
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 aZGRAuLFAfW9 for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 10:37:03 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (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 5782C1B2AD1 for <opsawg@ietf.org>; Fri, 13 Nov 2015 10:37:02 -0800 (PST)
Received: by ykfs79 with SMTP id s79so161978955ykf.1 for <opsawg@ietf.org>; Fri, 13 Nov 2015 10:37:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari_net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iZAIqC49JedPQLWd8zw6drKOpK8Q8AaV7CZqeytXrYs=; b=n4upfMYf19LG15vnXaovRAhddSOy7WS/WBDdAv8yjf7ilNTcpem/N1J+kFrok9C0WB EdvwDmdm2df9i3xlXtcRgRRFSB68SdlUfH7ZDedrmVwmIZtcoVdFEarXJjJaj66Jvy8s 4nKYEMkKLUbmdhqu2I78Rb90hA0hON7uPPhmGcjPheZWCIZ+LCeCeKHhApd1WOkVl47O 5xZUdlCTWdGlyV48oLAEtyts054LWVzkvB0FGR/MhLmEVy7eSAC8nSfg+b02WZi3xNHH vz4Tz4RmhfFHLuCSe41qN+oqDbSbu4driPLLL/hvIa3/Dr9Si0LvW8hU5jRqwhSApt0A 1NPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=iZAIqC49JedPQLWd8zw6drKOpK8Q8AaV7CZqeytXrYs=; b=m6bOsCgSL5JGRf46ieD9TCZxVXFy6PVVhucx5YxIVzGmJgeFQE9oZxyH1I1g9ipKfq rfqR+ZMcm718jpo1+lECf2+Ume2M0XIjU4PHJozhWqo8Y1Lc07ppFjdlU8o6XmYBdXSV DznASqoEN1K3a1uF6bMVNTDbqU8s3R3FtuCUlyX8KJ75PHeMn3bcUnIDHuoAectziSob EXsFzerkElAtjIeRHWqZT3Ifo+yBF3Ak75HkeH55rkRwNgoEEbgv1Pm9o6ibFyggqwY0 LsphlCGkxAZe3c5UMV3+ki1ghgH7ZmYx+maTAke1OM4+ZVnmuDRjIeYviTzbQFmuw5L0 KVhg==
X-Gm-Message-State: ALoCoQk8r55PkVnz0sxmzI+aMCwL/g2V24r64JI3UWlq38zB9ybWjFcO9ptzt4i9Whl73PLtorHS
MIME-Version: 1.0
X-Received: by 10.129.98.5 with SMTP id w5mr6943403ywb.333.1447439821641; Fri, 13 Nov 2015 10:37:01 -0800 (PST)
Received: by 10.37.202.11 with HTTP; Fri, 13 Nov 2015 10:37:01 -0800 (PST)
In-Reply-To: <D237455F.BC00F%dcmgash@cisco.com>
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com>
Date: Fri, 13 Nov 2015 13:37:01 -0500
Message-ID: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/gUCbeAHStuH6fm5JV_9pcJpfYv4>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 18:37:04 -0000

We would really appreciate any feedback on this document. Personally I
think it is really useful, but we need the WG to review and provide
feedback.

Over the years I've heard a number of people kvetch that TACACS+ isn't
documented -- well, now you can, you know, actually do something about
this...

W

On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
<dcmgash@cisco.com> wrote:
> Dear Opsawg List,
>
> We have uploaded a second revision of the TACACS+ protocol specification
> which we believe is ready for publication subject subject to port
> allocation.
>
> Please see details below.
>
> The essential difference from the first revision is the change of TLS
> option support using a separate port as opposed to the original Start TLS
> mechanism.
>
> We would be very grateful for the opinion of the list regarding the
> suitability of document for publication as an RFC.
>
> Many thanks,
>
> Thorsten, Andrej, Doug.
>
>
> On 02/10/2015 16:25, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
>>
>>A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
>>has been successfully submitted by Douglas C. Medway Gash and posted to
>>the
>>IETF repository.
>>
>>Name:          draft-dahm-opsawg-tacacs
>>Revision:      01
>>Title:         The TACACS+ Protocol
>>Document date: 2015-10-02
>>Group:         Individual Submission
>>Pages:         38
>>URL:
>>https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
>>Status:         https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
>>Htmlized:       https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
>>Diff:
>>https://www.ietf.org/rfcdiff?url2=draft-dahm-opsawg-tacacs-01
>>
>>Abstract:
>>   TACACS+ provides access control for routers, network access servers
>>   and other networked computing devices via one or more centralized
>>   servers.  TACACS+ provides separate authentication, authorization and
>>   accounting services.  This document describes the protocol that is
>>   used by TACACS+.
>>
>>
>>
>>
>>
>>Please note that it may take a couple of minutes from the time of
>>submission
>>until the htmlized version and diff are available at tools.ietf.org.
>>
>>The IETF Secretariat
>>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Fri Nov 13 10:44:07 2015
Return-Path: <heas@shrubbery.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB7D1B2B3E for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 10:44:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.726
X-Spam-Level: 
X-Spam-Status: No, score=-2.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fLFSVTbr6VfE for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 10:44:04 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id C35981B2B3B for <opsawg@ietf.org>; Fri, 13 Nov 2015 10:44:04 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 718F41196E6; Fri, 13 Nov 2015 18:44:04 +0000 (UTC)
Date: Fri, 13 Nov 2015 18:44:04 +0000
From: heasley <heas@shrubbery.net>
To: opsawg@ietf.org
Message-ID: <20151113184404.GH81506@shrubbery.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/MVO-UF5j3tRghMrZR4ozdHprlyc>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 18:44:06 -0000

> We would really appreciate any feedback on this document. Personally I
> think it is really useful, but we need the WG to review and provide
> feedback.

I have read this draft and support publication.

> On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
> <dcmgash@cisco.com> wrote:
> > Dear Opsawg List,
> >
> > We have uploaded a second revision of the TACACS+ protocol specification
> > which we believe is ready for publication subject subject to port
> > allocation.
> >
> > Please see details below.
> >
> > The essential difference from the first revision is the change of TLS
> > option support using a separate port as opposed to the original Start TLS
> > mechanism.
> >
> > We would be very grateful for the opinion of the list regarding the
> > suitability of document for publication as an RFC.
> >
> > Many thanks,
> >
> > Thorsten, Andrej, Doug.
> >
> >
> > On 02/10/2015 16:25, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> > wrote:
> >
> >>
> >>A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
> >>has been successfully submitted by Douglas C. Medway Gash and posted to
> >>the
> >>IETF repository.
> >>
> >>Name:          draft-dahm-opsawg-tacacs
> >>Revision:      01
> >>Title:         The TACACS+ Protocol
> >>Document date: 2015-10-02
> >>Group:         Individual Submission
> >>Pages:         38
> >>URL:
> >>https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
> >>Status:         https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
> >>Htmlized:       https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
> >>Diff:
> >>https://www.ietf.org/rfcdiff?url2=draft-dahm-opsawg-tacacs-01
> >>
> >>Abstract:
> >>   TACACS+ provides access control for routers, network access servers
> >>   and other networked computing devices via one or more centralized
> >>   servers.  TACACS+ provides separate authentication, authorization and
> >>   accounting services.  This document describes the protocol that is
> >>   used by TACACS+.
> >>
> >>
> >>
> >>
> >>
> >>Please note that it may take a couple of minutes from the time of
> >>submission
> >>until the htmlized version and diff are available at tools.ietf.org.
> >>
> >>The IETF Secretariat


From nobody Fri Nov 13 18:58:36 2015
Return-Path: <guy@alum.mit.edu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235841B37B0 for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 18:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no
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 drt9UAnWhcYR for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2015 18:58:32 -0800 (PST)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 2EAEC1B37AD for <opsawg@ietf.org>; Fri, 13 Nov 2015 18:58:31 -0800 (PST)
Received: from [192.168.42.66] (173-228-4-166.dsl.dynamic.fusionbroadband.com [173.228.4.166]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tAE2wSDo027402 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 13 Nov 2015 18:58:29 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Guy Harris <guy@alum.mit.edu>
In-Reply-To: <29455.1447345596@sandelman.ca>
Date: Fri, 13 Nov 2015 18:58:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5374DBCB-12AB-4625-B126-D48E7058DD51@alum.mit.edu>
References: <28578.1447203925@sandelman.ca> <E942894B-FDD3-41D3-8DAA-BFBDADB56EEE@alum.mit.edu> <29455.1447345596@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.2104)
X-Sonic-CAuth: UmFuZG9tSVaG1DnMTBkCxl6YtQEDfSeVOtrtgFPbAD/XVokAx9iH36t1v4JODr8gq5EDCOWKOFM2tFRdX0KTnb5hefRBLdMX
X-Sonic-ID: C;MuKMlHuK5RGASr0U9jFv0A== M;mCHxlHuK5RGASr0U9jFv0A==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/iYwJd1HKAcMTRgNv9m5nR9WtBOA>
Cc: Pcap-ng file format <pcap-ng-format@winpcap.org>, opsawg@ietf.org, dominique barthel <dominique.barthel@orange-ftgroup.com>, tcpdump-workers <tcpdump-workers@lists.tcpdump.org>
Subject: Re: [OPSAWG] [tcpdump-workers] [pcap-ng-format] comments/edits on pcapng
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Nov 2015 02:58:34 -0000

On Nov 12, 2015, at 8:26 AM, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:

> Guy Harris <guy@alum.mit.edu> wrote:
>=20

>> I don't see what the problem is with different block types having
>> different option name spaces.  Common code to handle options in all
>> block types wouldn't be that useful - that code wouldn't, for =
example,
>> be able to do anything useful with the interface speed option in a =
Name
>> Resolution Block.  (And what do you mean by a "comment block"; we =
don't
>> have blocks whose sole purpose is to contain comments, we have a
>> comment option that can be used in any block, the content of which is
>> solely intended for display to humans.)
>=20
> Perhaps I've mis-understood how these suboptions work.

The idea is that each block type has its own set of options, with every =
set being required to include an option numbered 0 for "end of options" =
and an option numbered 1 for "UTF-8 comment string".  Code to read a =
particular block type handles all the options for that block type, =
including options 0 and 1; the code to read option 1 is simple, it's the =
code to *display* it that does most of the work, and that'd probably be =
different for different block types anyway.

>>> On the subject of the Encryption Block.  In discussion on the list
>>> many asked if we needed it.  Let me suggest that we do, but that =
yes,
>>> we need more information in it.
>=20
>> Well, the first question is what sort of information would be put in
>> it.  The current spec just says it "is used to store encrypted data"
>> and says of the data in it that "Once decrypted, it originates other
>> blocks.", but it doesn't say what sort of stuff is being encrypted!
>> Lists of credit card numbers? :-)
>=20
> I think that essentially, it encrypts other blocks, such as captures, =
etc.

We should probably indicate that, then, rather than just vaguely stating =
"An Encryption Block is used to store encrypted data." and "Encrypted =
Data: data of this block. Once decrypted, it originates other blocks."

Or perhaps we should remove it from the spec, and put something back in =
once it's finalized to the point of having a block number assigned and =
having an indication of what it contains and how it should be handled by =
readers.

>>> Now, about LinkType: I suggest that having libpcap/tcpdump continue =
to
>>> maintain the table is not ideal.  Instead, let's create an IANA
>>> registry for it, populate it with existing values, and make the
>>> libpcap group the Expert Review.
>=20
>> So where would the actual formats be made available?
>=20
> We'd have to include a few key ones into this document, and the rest =
would
> continue to have the rather loose references that the web site has =
now.

The Web site also stores a few specs linked to from entries in the table =
at

	http://www.tcpdump.org/linktypes.html

for formats for which there's no spec to point to elsewhere on the Web; =
where should those specs be stored?

In addition, the description column in that table has some fairly long =
entries, which look longer than the sort of things that show up in IANA =
registries such as

	=
http://www.iana.org/assignments/snoop-datalink-types/snoop-datalink-types.=
xhtml#snoop-datalink-types-2

That table just points to RFCs, and the main RFC:

	http://tools.ietf.org/html/rfc1761

just has a rather terse table:

        Datalink Type:

                A 32-bit (4 octet) field identifying the type of
                datalink header used in the packet records that follow.
                The datalink type codes are listed in the table below:

                Datalink Type           Code
                -------------           ----
                IEEE 802.3              0
                IEEE 802.4 Token Bus    1
                IEEE 802.5 Token Ring   2
                IEEE 802.6 Metro Net    3
                Ethernet                4
                HDLC                    5
                Character Synchronous   6
                IBM Channel-to-Channel  7
                FDDI                    8
                Other                   9
                Unassigned              10 - 4294967295

most of the entries of which are probably sufficient (i.e., they just =
contain a frame for the particular LAN/MAN technology, with nothing =
added, subtracted, or rearranged), but "HDLC", "Character Synchronous", =
and "IBM Channel-to-Channel" are too vague to actually be useful.  That =
might be because those DLPI types were reserved for those purposes but =
never actually officially *used* for those purposes, and thus nobody had =
to figure out what the format of those packets were.

We could publish an RFC containing the current set of link-layer header =
types from the tcpdump.org site, perhaps including the text from the =
specs stored on tcpdump.org, and refer to that from the pcap-ng spec =
*and* from any pcap spec we publish as an I-D or RFC; I'd have it give =
the descriptions from the tcpdump.org site, to be a little more =
restrictive than the snoop spec - I'd rather not have to throw =
heuristics into tcpdump or Wireshark to distinguish between packets =
using one interpretation of the description of LINKTYPE_FOOBAR and =
packets using another interpretation.

>> I don't think an RFC is required as a reference, so we wouldn't have =
to
>> wait for an RFC to percolate through the process before making a new
>> link-layer header type available, but that would leave open the
>> question of what to use as a reference until the RFC comes out, and =
if
>> you don't want www.tcpdump.org to store the description until it =
shows
>> up in an RFC...
>=20
> So, what happens right now is that we do Expert Review.  People ask us =
for a
> link type, and we beat on them a bit to give a slightly stable =
document to
> point at, or at least to argue why no existing type works for them.
> Then they get the number, and if we are lucky, we also have a stable =
link to
> their format.  With IANA Expert Review, we could essentially do =
exactly the
> same thing --- just that IANA would write down the result.
>=20
> Numbers can be assigned by RFC as well, and can be assigned early, and =
IANA
> is happy to change the reference from draft-foo-bar to RFCxyaz as the
> document progresses.

So it sounds as if we can assign a number before the RFC is issued for a =
new block type/link type/option code/etc., and update the registry when =
an I-D is issued or updated or an RFC is issued.

> But, it can also just be a link to =
http://www.company.com/technote/foo.html,
> or it can, as it says now, say, "Used by Company XYZ for Proprietary =
FOO"

So presumably somebody who wants a link type would go to

	http://www.iana.org/form/protocol-assignment

and request one.

So does a Designated Expert for a registry get to edit whatever =
underlying file or database is used to generate pages for the registry =
in question?  I.e., what would the Designated Expert do when adding a =
new block type/link type/option/etc.?  Is there a repository to which =
they're granted access and to which they do a commit/push/whatever with =
the update?  Is it a database for which there's some Web interface to =
publish updates?

Or does the Designated Expert send a request to somebody at the IANA, =
who updates the file/database/whatever?

I assume the actual underlying mechanism that implements the Protocol =
Assignment registry pages is documented *somewhere*.=


From nobody Sat Nov 14 22:18:01 2015
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD5581B4042 for <opsawg@ietfa.amsl.com>; Sat, 14 Nov 2015 22:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 48_D9-E9i3Oy for <opsawg@ietfa.amsl.com>; Sat, 14 Nov 2015 22:17:48 -0800 (PST)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 D280F1B4048 for <opsawg@ietf.org>; Sat, 14 Nov 2015 22:17:47 -0800 (PST)
Received: by igvg19 with SMTP id g19so58263276igv.1 for <opsawg@ietf.org>; Sat, 14 Nov 2015 22:17:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=pZPETn++/wZ15WIgQsJLDJDXQPSc9mUsVf5n+40a95Q=; b=TisIif4dBK8aN9B9jdtsUe8mnAY5bHs4y3H8Qy/4EoxA+hn7GFrW67yfYGZ3HivZ40 yqQzqviXXnYMLLuBf9uGp4XPy0AZYS5bIhj+0iAy7JdJR96mbAQp9svXGUZO077S6vED A3wEvm39PcPA0jMLR31VKNGJ/EY7l2D0my9uN5WaL8MGgSvWfo7bSwHznyZhanuB88WZ T1WUhSBesQttuLjrOsg1b7WFRjKMsCcNODDwAYQrjsHoCUEPqffjQO3XppVhvuTekXEm taeFo/CZ8fBztxOJqVnw4xi+LprmMj2wvknLn9WaHD5Mi5Z5Ld/ysfOqkhHh5tmYEvVm GOVg==
X-Received: by 10.50.131.229 with SMTP id op5mr10810103igb.83.1447568267192; Sat, 14 Nov 2015 22:17:47 -0800 (PST)
Received: from still.local ([184.13.114.26]) by smtp.googlemail.com with ESMTPSA id 126sm1127351ion.32.2015.11.14.22.17.46 for <opsawg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Nov 2015 22:17:46 -0800 (PST)
To: opsawg@ietf.org
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <56482389.20509@gmail.com>
Date: Sun, 15 Nov 2015 01:17:45 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Thunderbird/42.0a2
MIME-Version: 1.0
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/zrZdCi-lO5cFGIsqtJWWwpXmIC4>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Nov 2015 06:17:55 -0000

Okay, I spent some time reviewing this document and yes, it's actually 
useful stuff.  it should be adopted.

tim


On 11/13/15 1:37 PM, Warren Kumari wrote:
> We would really appreciate any feedback on this document. Personally I
> think it is really useful, but we need the WG to review and provide
> feedback.
>
> Over the years I've heard a number of people kvetch that TACACS+ isn't
> documented -- well, now you can, you know, actually do something about
> this...
>
> W
>
> On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
> <dcmgash@cisco.com> wrote:
>> Dear Opsawg List,
>>
>> We have uploaded a second revision of the TACACS+ protocol specification
>> which we believe is ready for publication subject subject to port
>> allocation.
>>
>> Please see details below.
>>
>> The essential difference from the first revision is the change of TLS
>> option support using a separate port as opposed to the original Start TLS
>> mechanism.
>>
>> We would be very grateful for the opinion of the list regarding the
>> suitability of document for publication as an RFC.
>>
>> Many thanks,
>>
>> Thorsten, Andrej, Doug.
>>
>>
>> On 02/10/2015 16:25, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>> wrote:
>>
>>>
>>> A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
>>> has been successfully submitted by Douglas C. Medway Gash and posted to
>>> the
>>> IETF repository.
>>>
>>> Name:          draft-dahm-opsawg-tacacs
>>> Revision:      01
>>> Title:         The TACACS+ Protocol
>>> Document date: 2015-10-02
>>> Group:         Individual Submission
>>> Pages:         38
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
>>> Htmlized:       https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
>>> Diff:
>>> https://www.ietf.org/rfcdiff?url2=draft-dahm-opsawg-tacacs-01
>>>
>>> Abstract:
>>>    TACACS+ provides access control for routers, network access servers
>>>    and other networked computing devices via one or more centralized
>>>    servers.  TACACS+ provides separate authentication, authorization and
>>>    accounting services.  This document describes the protocol that is
>>>    used by TACACS+.
>>>
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>
>
>
>


From nobody Mon Nov 16 04:27:09 2015
Return-Path: <evyncke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C04EF1A8A71 for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 04:27:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level: 
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FdRPMiNJwibR for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 04:27:06 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26BE71A8A6D for <opsawg@ietf.org>; Mon, 16 Nov 2015 04:27:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4430; q=dns/txt; s=iport; t=1447676826; x=1448886426; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=R3dGisIFmrSmW4r4LcQ/aqoi9h3SxkxbdIiikPlAkSg=; b=Cv61jAWMCzeV3K0TX3B44MxjMElu4OQxEDBh6MRe6u+F50fykvu2gF+1 YVbO/hRU6rVr7CvN7LnSOmtttG76kJLq4RW/092dOTJGy1y/z3NQWr+lX wF2An1euV1K5tDlP/GLJNHTT3aGVEZFRfc4hUkFoR15e0oDV5eAT1GYUG o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ARAgC7yklW/5FdJa1egztTbwa+TwENg?= =?us-ascii?q?WQXCoUlSgIcgR04FAEBAQEBAQGBCoQ0AQEBBAEBASAROgkSAgEIGAICJgICAiU?= =?us-ascii?q?LFQcJAgQBEoguDaoKkAQBAQEBAQEBAQEBAQEBAQEBAQEBGoEBhVMBhH2EWRiDB?= =?us-ascii?q?IFEBY0bhUyDYQGFHIgKgVtJg3eSOINxAR8BAUKEBHIBhEOBBwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.20,302,1444694400"; d="scan'208";a="45366703"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-8.cisco.com with ESMTP; 16 Nov 2015 12:27:05 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id tAGCR4lk019513 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 16 Nov 2015 12:27:05 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 Nov 2015 07:27:04 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.000; Mon, 16 Nov 2015 07:27:04 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Warren Kumari <warren@kumari.net>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
Thread-Index: AQHRIGoZhYnX54dRC0O+u0h5E2XoPg==
Date: Mon, 16 Nov 2015 12:27:04 +0000
Message-ID: <D26F8962.5E2B9%evyncke@cisco.com>
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.8.151023
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.138.46]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E4A46C8ED1EB6846B223234F91243A74@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ejHB1Ldm8GTty5GK2PH7eIi9qho>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 12:27:07 -0000

SW1wb3J0YW50IGRvY3VtZW50IGluZGVlZC4NCg0KSSBoYXZlIGEgY29tbWVudCBvbiBzZWN0aW9u
IDcuMSB3aGVyZSAiaXAiIGFzIGEgcHJvdG9jb2wgKHRoZSBkb3VibGUNCnF1b3RlcyBhcmUgZnJv
bSB0aGUgSS1EKSBpcyBtZW50aW9uZWQgYnV0IGRvZXMgaXQgbWVhbiBJUHY0IG9yIElQdjYgb3IN
CmJvdGg/DQoNCkluIHRoZSBzYW1lIHNlY3Rpb24sIG1heSBJIHN1Z2dlc3QgdG8gZGVzY3JpYmUg
dGhlIHN5bnRheCBvZiB0aGUgJ2FkZHInDQpmaWVsZD8NCg0KSG9wZSB0aGlzIGhlbHBzIHRvIGlu
Y3JlYXNlIHRoZSBxdWFsaXR5IG9mIHRoaXMgaW1wb3J0YW50IEktRA0KDQotw6lyaWMNCg0KDQpP
biAxMy8xMS8xNSAxOTozNywgIk9QU0FXRyBvbiBiZWhhbGYgb2YgV2FycmVuIEt1bWFyaSINCjxv
cHNhd2ctYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2Ygd2FycmVuQGt1bWFyaS5uZXQ+IHdy
b3RlOg0KDQo+V2Ugd291bGQgcmVhbGx5IGFwcHJlY2lhdGUgYW55IGZlZWRiYWNrIG9uIHRoaXMg
ZG9jdW1lbnQuIFBlcnNvbmFsbHkgSQ0KPnRoaW5rIGl0IGlzIHJlYWxseSB1c2VmdWwsIGJ1dCB3
ZSBuZWVkIHRoZSBXRyB0byByZXZpZXcgYW5kIHByb3ZpZGUNCj5mZWVkYmFjay4NCj4NCj5PdmVy
IHRoZSB5ZWFycyBJJ3ZlIGhlYXJkIGEgbnVtYmVyIG9mIHBlb3BsZSBrdmV0Y2ggdGhhdCBUQUNB
Q1MrIGlzbid0DQo+ZG9jdW1lbnRlZCAtLSB3ZWxsLCBub3cgeW91IGNhbiwgeW91IGtub3csIGFj
dHVhbGx5IGRvIHNvbWV0aGluZyBhYm91dA0KPnRoaXMuLi4NCj4NCj5XDQo+DQo+T24gU3VuLCBP
Y3QgNCwgMjAxNSBhdCA0OjE4IFBNLCBEb3VnbGFzIEdhc2ggKGRjbWdhc2gpDQo+PGRjbWdhc2hA
Y2lzY28uY29tPiB3cm90ZToNCj4+IERlYXIgT3BzYXdnIExpc3QsDQo+Pg0KPj4gV2UgaGF2ZSB1
cGxvYWRlZCBhIHNlY29uZCByZXZpc2lvbiBvZiB0aGUgVEFDQUNTKyBwcm90b2NvbCBzcGVjaWZp
Y2F0aW9uDQo+PiB3aGljaCB3ZSBiZWxpZXZlIGlzIHJlYWR5IGZvciBwdWJsaWNhdGlvbiBzdWJq
ZWN0IHN1YmplY3QgdG8gcG9ydA0KPj4gYWxsb2NhdGlvbi4NCj4+DQo+PiBQbGVhc2Ugc2VlIGRl
dGFpbHMgYmVsb3cuDQo+Pg0KPj4gVGhlIGVzc2VudGlhbCBkaWZmZXJlbmNlIGZyb20gdGhlIGZp
cnN0IHJldmlzaW9uIGlzIHRoZSBjaGFuZ2Ugb2YgVExTDQo+PiBvcHRpb24gc3VwcG9ydCB1c2lu
ZyBhIHNlcGFyYXRlIHBvcnQgYXMgb3Bwb3NlZCB0byB0aGUgb3JpZ2luYWwgU3RhcnQNCj4+VExT
DQo+PiBtZWNoYW5pc20uDQo+Pg0KPj4gV2Ugd291bGQgYmUgdmVyeSBncmF0ZWZ1bCBmb3IgdGhl
IG9waW5pb24gb2YgdGhlIGxpc3QgcmVnYXJkaW5nIHRoZQ0KPj4gc3VpdGFiaWxpdHkgb2YgZG9j
dW1lbnQgZm9yIHB1YmxpY2F0aW9uIGFzIGFuIFJGQy4NCj4+DQo+PiBNYW55IHRoYW5rcywNCj4+
DQo+PiBUaG9yc3RlbiwgQW5kcmVqLCBEb3VnLg0KPj4NCj4+DQo+PiBPbiAwMi8xMC8yMDE1IDE2
OjI1LCAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIg0KPj48aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnPg0KPj4gd3JvdGU6DQo+Pg0KPj4+DQo+Pj5BIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQt
ZGFobS1vcHNhd2ctdGFjYWNzLTAxLnR4dA0KPj4+aGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1p
dHRlZCBieSBEb3VnbGFzIEMuIE1lZHdheSBHYXNoIGFuZCBwb3N0ZWQgdG8NCj4+PnRoZQ0KPj4+
SUVURiByZXBvc2l0b3J5Lg0KPj4+DQo+Pj5OYW1lOiAgICAgICAgICBkcmFmdC1kYWhtLW9wc2F3
Zy10YWNhY3MNCj4+PlJldmlzaW9uOiAgICAgIDAxDQo+Pj5UaXRsZTogICAgICAgICBUaGUgVEFD
QUNTKyBQcm90b2NvbA0KPj4+RG9jdW1lbnQgZGF0ZTogMjAxNS0xMC0wMg0KPj4+R3JvdXA6ICAg
ICAgICAgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+Pj5QYWdlczogICAgICAgICAzOA0KPj4+VVJM
Og0KPj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWRhaG0tb3Bz
YXdnLXRhY2Fjcy0wMS50eHQNCj4+PlN0YXR1czogICAgICAgICANCj4+Pmh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWRhaG0tb3BzYXdnLXRhY2Fjcy8NCj4+Pkh0bWxpemVk
OiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZGFobS1vcHNhd2ctdGFj
YWNzLTAxDQo+Pj5EaWZmOg0KPj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRy
YWZ0LWRhaG0tb3BzYXdnLXRhY2Fjcy0wMQ0KPj4+DQo+Pj5BYnN0cmFjdDoNCj4+PiAgIFRBQ0FD
UysgcHJvdmlkZXMgYWNjZXNzIGNvbnRyb2wgZm9yIHJvdXRlcnMsIG5ldHdvcmsgYWNjZXNzIHNl
cnZlcnMNCj4+PiAgIGFuZCBvdGhlciBuZXR3b3JrZWQgY29tcHV0aW5nIGRldmljZXMgdmlhIG9u
ZSBvciBtb3JlIGNlbnRyYWxpemVkDQo+Pj4gICBzZXJ2ZXJzLiAgVEFDQUNTKyBwcm92aWRlcyBz
ZXBhcmF0ZSBhdXRoZW50aWNhdGlvbiwgYXV0aG9yaXphdGlvbiBhbmQNCj4+PiAgIGFjY291bnRp
bmcgc2VydmljZXMuICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyB0aGUgcHJvdG9jb2wgdGhhdCBp
cw0KPj4+ICAgdXNlZCBieSBUQUNBQ1MrLg0KPj4+DQo+Pj4NCj4+Pg0KPj4+DQo+Pj4NCj4+PlBs
ZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0
aW1lIG9mDQo+Pj5zdWJtaXNzaW9uDQo+Pj51bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQg
ZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPj4+DQo+Pj5UaGUgSUVURiBT
ZWNyZXRhcmlhdA0KPj4+DQo+Pg0KPg0KPg0KPg0KPi0tIA0KPkkgZG9uJ3QgdGhpbmsgdGhlIGV4
ZWN1dGlvbiBpcyByZWxldmFudCB3aGVuIGl0IHdhcyBvYnZpb3VzbHkgYSBiYWQNCj5pZGVhIGlu
IHRoZSBmaXJzdCBwbGFjZS4NCj5UaGlzIGlzIGxpa2UgcHV0dGluZyByYWJpZCB3ZWFzZWxzIGlu
IHlvdXIgcGFudHMsIGFuZCBsYXRlciBleHByZXNzaW5nDQo+cmVncmV0IGF0IGhhdmluZyBjaG9z
ZW4gdGhvc2UgcGFydGljdWxhciByYWJpZCB3ZWFzZWxzIGFuZCB0aGF0IHBhaXINCj5vZiBwYW50
cy4NCj4gICAtLS1tYWYNCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPk9QU0FXRyBtYWlsaW5nIGxpc3QNCj5PUFNBV0dAaWV0Zi5vcmcNCj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29wc2F3Zw0KDQo=


From nobody Mon Nov 16 11:20:06 2015
Return-Path: <owen@delong.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED761A8836 for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.686
X-Spam-Level: 
X-Spam-Status: No, score=-6.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
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 vsdF19FP3UZj for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:20:04 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id C95F21A8830 for <opsawg@ietf.org>; Mon, 16 Nov 2015 11:20:02 -0800 (PST)
Received: from delong-dhcp229.delong.com (delong-dhcp29 [192.159.10.229]) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tAGJHvfR016208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 16 Nov 2015 11:17:57 -0800
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <D26F8962.5E2B9%evyncke@cisco.com>
Date: Mon, 16 Nov 2015 11:17:57 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA3ADF0B-DF22-40B4-96EB-B92EE6B524A0@delong.com>
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com> <D26F8962.5E2B9%evyncke@cisco.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/L08xYdotOFJf5BeM_RmfiZgPIkM>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 19:20:05 -0000

> On Nov 16, 2015, at 04:27 , Eric Vyncke (evyncke) <evyncke@cisco.com> =
wrote:
>=20
> Important document indeed.
>=20
> I have a comment on section 7.1 where "ip" as a protocol (the double
> quotes are from the I-D) is mentioned but does it mean IPv4 or IPv6 or
> both?

Surely one would hope that it=E2=80=99s meaning is contextual to the =
time of reading
and that today it would mean {IPv4, IPv6} and that sometime in the =
future,
it will likely mean {IPv6} and beyond that come to mean {IPv6,=E2=80=A6}.

>=20
> In the same section, may I suggest to describe the syntax of the =
'addr'
> field?

Wouldn=E2=80=99t the syntax of the addr field be inherently dependent on =
the
RFC defining the IP version in question in the previous context?

Owen



From nobody Mon Nov 16 11:48:58 2015
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710E61A88B4 for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level: 
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 43Vg50dohUlz for <opsawg@ietfa.amsl.com>; Mon, 16 Nov 2015 11:48:55 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 090681A88CE for <opsawg@ietf.org>; Mon, 16 Nov 2015 11:48:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2751; q=dns/txt; s=iport; t=1447703315; x=1448912915; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=qXrVjuHbQnw6/pYCCM/KR6XM9ztOR4mVv1Sq2pkbvqQ=; b=LR+EWcJaVUJxFJrMF//4j4/JQtG3c4whLPhoDvr/spN5vzdyuECIXomf pEynmEwPWAMF/EJKoCETtJbAidjFs0rkmOtIMESN1eX5ScuWS+TerKMak 7c89ke6ph8zAaC9ig+Ee+zagHFDsJZ4cQkKjxXsLYV/j9am3+8kRaak5h Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AWAgBFMkpW/4ENJK1dgztTb7xGghoBD?= =?us-ascii?q?YFlIYVvAoFHOBQBAQEBAQEBgQqENAEBAQMBOD8BEQsYCRYPCQMCAQIBPAkGAQw?= =?us-ascii?q?GAgEBiCIIDbsfAQEBAQEBAQEBAQEBAQEBAQEBARqGVIR+iTkBBI0bdog3hR2IC?= =?us-ascii?q?oFbSYN3gwIjjxODch8BAUKEIiA0AYUJAQEB?=
X-IronPort-AV: E=Sophos;i="5.20,304,1444694400"; d="scan'208";a="208947567"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Nov 2015 19:48:35 +0000
Received: from [10.117.46.173] (rtp-jclarke-89112.cisco.com [10.117.46.173]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id tAGJmYhg005744; Mon, 16 Nov 2015 19:48:35 GMT
To: Warren Kumari <warren@kumari.net>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <564A3312.4030103@cisco.com>
Date: Mon, 16 Nov 2015 14:48:34 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ieYRV0FVoAfQNtFj-mwPUVx8l7c>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 19:48:56 -0000

On 11/13/15 13:37, Warren Kumari wrote:
> We would really appreciate any feedback on this document. Personally I
> think it is really useful, but we need the WG to review and provide
> feedback.
>
> Over the years I've heard a number of people kvetch that TACACS+ isn't
> documented -- well, now you can, you know, actually do something about
> this...

I may be biased, but I have read the doc, and I support the WG working 
on it.  I agree with your last sentiment that this would be good to 
final document this with industry consensus.

One thing I wonder is if there shouldn't be some version change for the 
support of TLS, or if the Type of 0x00 is enough?

Joe

>
> W
>
> On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
> <dcmgash@cisco.com> wrote:
>> Dear Opsawg List,
>>
>> We have uploaded a second revision of the TACACS+ protocol specification
>> which we believe is ready for publication subject subject to port
>> allocation.
>>
>> Please see details below.
>>
>> The essential difference from the first revision is the change of TLS
>> option support using a separate port as opposed to the original Start TLS
>> mechanism.
>>
>> We would be very grateful for the opinion of the list regarding the
>> suitability of document for publication as an RFC.
>>
>> Many thanks,
>>
>> Thorsten, Andrej, Doug.
>>
>>
>> On 02/10/2015 16:25, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>> wrote:
>>
>>>
>>> A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
>>> has been successfully submitted by Douglas C. Medway Gash and posted to
>>> the
>>> IETF repository.
>>>
>>> Name:          draft-dahm-opsawg-tacacs
>>> Revision:      01
>>> Title:         The TACACS+ Protocol
>>> Document date: 2015-10-02
>>> Group:         Individual Submission
>>> Pages:         38
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
>>> Htmlized:       https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
>>> Diff:
>>> https://www.ietf.org/rfcdiff?url2=draft-dahm-opsawg-tacacs-01
>>>
>>> Abstract:
>>>    TACACS+ provides access control for routers, network access servers
>>>    and other networked computing devices via one or more centralized
>>>    servers.  TACACS+ provides separate authentication, authorization and
>>>    accounting services.  This document describes the protocol that is
>>>    used by TACACS+.
>>>
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>
>
>
>


From nobody Thu Nov 19 05:51:43 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94D801B29C0; Thu, 19 Nov 2015 05:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.484
X-Spam-Level: 
X-Spam-Status: No, score=-7.484 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585] autolearn=ham
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 mAehLqOy1SLu; Thu, 19 Nov 2015 05:51:26 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B18EC1AD4A1; Thu, 19 Nov 2015 05:51:25 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AeAwBBP8ZV/xUHmMZbGQGCNCEsVG+pbgaTNgmCBIV5AoEmOBQBAQEBAQEBgQqEJQEBAxIbTBIBDAkVViYBBAENDREJiAwBDKxsoD4BAQEBAQEBAwEBAQEBAQEBARUEhh+JaQEBHy0Egx+BFAWVCwFthBSJKocwjR6DZhcPg32BfTqBBAEBAQ
X-IPAS-Result: A2AeAwBBP8ZV/xUHmMZbGQGCNCEsVG+pbgaTNgmCBIV5AoEmOBQBAQEBAQEBgQqEJQEBAxIbTBIBDAkVViYBBAENDREJiAwBDKxsoD4BAQEBAQEBAwEBAQEBAQEBARUEhh+JaQEBHy0Egx+BFAWVCwFthBSJKocwjR6DZhcPg32BfTqBBAEBAQ
X-IronPort-AV: E=Sophos;i="5.15,634,1432612800";  d="scan'208,217";a="129370299"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Nov 2015 08:51:22 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 19 Nov 2015 08:51:21 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Thu, 19 Nov 2015 08:51:20 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "opsec@ietf.org" <opsec@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Feedback on the SACM Vulnerability Assessment Scenario 
Thread-Index: AdEi0VjikxFfTlxYT32xzoHq98yx8w==
Date: Thu, 19 Nov 2015 13:51:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/rLRLyVejJHqameWCn4S4OFhZqBA>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: [OPSAWG] Feedback on the SACM Vulnerability Assessment Scenario
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 13:51:30 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I am reiterating a request that I made at IETF 94 in the OPSAWG meeting, an=
d also sent to the mail lists of opsec and opsawg. The SACM WG is consideri=
ng a document https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scena=
rio/ that describes the operational practice of vulnerability reports, whic=
h we believe is an important use case in the security assessment life cycle=
. We are requiring feedback from operators about the scenario describe in t=
his document - does it make sense? Is it similar with what you do in operat=
ional real life? Are you using similar or different methods for vulnerabili=
ty assessment in your networks? A quick reading and short feedback would be=
 greatly appreciated.

Thanks and Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am reiterating a request that I made at IETF 94 in=
 the OPSAWG meeting, and also sent to the mail lists of opsec and opsawg. T=
he SACM WG is considering a document
<a href=3D"https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario=
/">https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/</a> th=
at describes the operational practice of vulnerability reports, which we be=
lieve is an important use case in
 the security assessment life cycle. We are requiring feedback from operato=
rs about the scenario describe in this document &#8211; does it make sense?=
 Is it similar with what you do in operational real life? Are you using sim=
ilar or different methods for vulnerability
 assessment in your networks? A quick reading and short feedback would be g=
reatly appreciated.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7AZFFEXMB04globa_--


From nobody Thu Nov 19 12:36:31 2015
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A601B3516; Thu, 19 Nov 2015 12:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.785
X-Spam-Level: 
X-Spam-Status: No, score=-4.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
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 3CRn2C19IclA; Thu, 19 Nov 2015 12:36:26 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E41931B3514; Thu, 19 Nov 2015 12:36:25 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CAO45380; Thu, 19 Nov 2015 20:36:23 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 19 Nov 2015 20:36:22 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0235.001; Thu, 19 Nov 2015 12:36:20 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "opsec@ietf.org" <opsec@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Feedback on the SACM Vulnerability Assessment Scenario
Thread-Index: AdEi0VjikxFfTlxYT32xzoHq98yx8wANziBQ
Date: Thu, 19 Nov 2015 20:36:19 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657DA3D4B@dfweml701-chm>
References: <9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.213]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657DA3D4Bdfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.564E32C7.0286, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6f2a590b28fdc288726fb11171ac287a
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/WopvzXd6lMcLExN0hosPNMWlns4>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [OPSAWG] Feedback on the SACM Vulnerability Assessment Scenario
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 20:36:29 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F657DA3D4Bdfweml701chm_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Reading through the document has made me feel that the Title of the draft i=
s misleading.
Based on the title I was expecting to see the Vulnerability Assessment of v=
arious network scenarios, which will be very useful information for enterpr=
ise and service provider network administrators to put in adequate tools to=
 protect those vulnerability.

But the document only describes the procedure in authenticating a end user/=
points and states that you need to compare with the Vulnerability report (a=
lmost like a common sense ) without saying how and what.  I guess I had too=
 high the expectation, but a little disappointed of not finding the informa=
tion I was looking for.

Linda Dunbar



From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Romascanu, Dan (=
Dan)
Sent: Thursday, November 19, 2015 7:51 AM
To: opsec@ietf.org; opsawg@ietf.org
Cc: sacm@ietf.org
Subject: [OPSAWG] Feedback on the SACM Vulnerability Assessment Scenario

Hi,

I am reiterating a request that I made at IETF 94 in the OPSAWG meeting, an=
d also sent to the mail lists of opsec and opsawg. The SACM WG is consideri=
ng a document https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scena=
rio/ that describes the operational practice of vulnerability reports, whic=
h we believe is an important use case in the security assessment life cycle=
. We are requiring feedback from operators about the scenario describe in t=
his document - does it make sense? Is it similar with what you do in operat=
ional real life? Are you using similar or different methods for vulnerabili=
ty assessment in your networks? A quick reading and short feedback would be=
 greatly appreciated.

Thanks and Regards,

Dan


--_000_4A95BA014132FF49AE685FAB4B9F17F657DA3D4Bdfweml701chm_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Reading through the do=
cument has made me feel that the Title of the draft is misleading.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Based on the title I w=
as expecting to see the Vulnerability Assessment of various network scenari=
os, which will be very useful information for enterprise and service provid=
er network administrators to put in
 adequate tools to protect those vulnerability. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">But the document only =
describes the procedure in authenticating a end user/points and states that=
 you need to compare with the Vulnerability report (almost like a common se=
nse ) without saying how and what. &nbsp;I
 guess I had too high the expectation, but a little disappointed of not fin=
ding the information I was looking for.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Linda Dunbar<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> OPSAWG [=
mailto:opsawg-bounces@ietf.org]
<b>On Behalf Of </b>Romascanu, Dan (Dan)<br>
<b>Sent:</b> Thursday, November 19, 2015 7:51 AM<br>
<b>To:</b> opsec@ietf.org; opsawg@ietf.org<br>
<b>Cc:</b> sacm@ietf.org<br>
<b>Subject:</b> [OPSAWG] Feedback on the SACM Vulnerability Assessment Scen=
ario<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am reiterating a request that I made at IETF 94 in=
 the OPSAWG meeting, and also sent to the mail lists of opsec and opsawg. T=
he SACM WG is considering a document
<a href=3D"https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario=
/">https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/</a> th=
at describes the operational practice of vulnerability reports, which we be=
lieve is an important use case in
 the security assessment life cycle. We are requiring feedback from operato=
rs about the scenario describe in this document &#8211; does it make sense?=
 Is it similar with what you do in operational real life? Are you using sim=
ilar or different methods for vulnerability
 assessment in your networks? A quick reading and short feedback would be g=
reatly appreciated.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F657DA3D4Bdfweml701chm_--


From joshua.stevens@hpe.com  Thu Nov 19 19:39:52 2015
Return-Path: <joshua.stevens@hpe.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BFAC1A89C4; Thu, 19 Nov 2015 19:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 vS3T3UuUojX7; Thu, 19 Nov 2015 19:39:47 -0800 (PST)
Received: from g2t2354.austin.hp.com (g2t2354.austin.hp.com [15.217.128.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 236091A8A3D; Thu, 19 Nov 2015 19:39:41 -0800 (PST)
Received: from G2W4316.americas.hpqcorp.net (g2w4316.austin.hp.com [16.197.9.73]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g2t2354.austin.hp.com (Postfix) with ESMTPS id 8228E79; Fri, 20 Nov 2015 03:39:40 +0000 (UTC)
Received: from G2W4313.americas.hpqcorp.net (16.197.24.255) by G2W4316.americas.hpqcorp.net (16.197.9.73) with Microsoft SMTP Server (TLS) id 14.3.169.1; Fri, 20 Nov 2015 03:37:30 +0000
Received: from G2W2529.americas.hpqcorp.net ([169.254.1.101]) by G2W4313.americas.hpqcorp.net ([16.197.24.255]) with mapi id 14.03.0169.001; Fri, 20 Nov 2015 03:37:30 +0000
From: "Stevens, Josh (Cyber Security)" <joshua.stevens@hpe.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "opsec@ietf.org" <opsec@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [sacm] Feedback on the SACM Vulnerability Assessment Scenario
Thread-Index: AdEi0VjikxFfTlxYT32xzoHq98yx8wAN8l+Q
Date: Fri, 20 Nov 2015 03:37:29 +0000
Message-ID: <9DDB58C939D0974CAEB9F2A0A0FC15C109DD9470@G2W2529.americas.hpqcorp.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [16.193.232.24]
Content-Type: multipart/alternative; boundary="_000_9DDB58C939D0974CAEB9F2A0A0FC15C109DD9470G2W2529americas_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/pfcGQ3AN49YtXqg4Es4GscO3dsw>
X-Mailman-Approved-At: Thu, 19 Nov 2015 20:05:43 -0800
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [OPSAWG] [sacm] Feedback on the SACM Vulnerability Assessment Scenario
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2015 03:44:07 -0000

--_000_9DDB58C939D0974CAEB9F2A0A0FC15C109DD9470G2W2529americas_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Dan,

Agreed, this does help focus the work for this SACM Working Group.  After r=
eading the draft-coffin-sacm-vuln-scenario, I had some initial feedback fro=
m an enterprise defense perspective that might be incorporated.  Here are m=
y contributions:



1.       In the abstract, a vulnerability report is referenced, however it'=
s not clear whether an authenticated or unauthenticated vulnerability scan =
report (or both) is being referred to.  If it can consume both, I would cal=
l that out. If what's being referred to is actually a recurring industry st=
andard vulnerability report from a vendor, that could also clear up the abs=
tract prior to the scope statement where the vulnerability report is define=
d.



2.       In the abstract, there isn't a reference to the endpoint based app=
roach that is detailed in the next section. Ideally, instead of "It begins =
with an enterprise ingesting a vulnerability report and ends at the point o=
f identifying affected endpoints",  this could be better summarized as "End=
point data is pushed to a central point for comparison with vulnerability c=
riteria to enable posture assessment."



3.       3.3 A few comments on page 7, paragraph 4  "The attributes could b=
e manually entered into a CMDB by a human, This would include any attribute=
s that cannot be collected programmatically." I believe the intent here is =
to leave fields open for the user to define and leverage as needed, however=
 I'm not sure we want to advocate manual entry? Ideally, if we can use a co=
mmon set of algorithms that can be *manually* adjusted to provide exception=
 based rules to the overall effort.  If we give a user the chance to mangle=
 data sets, they probably will - I'm in favor of providing additional field=
s that can be interfaced with other security API's where automation is the =
default workflow choice.   Here are some alternatives to manual entry for t=
hese three categories:

a.       Location - for a global organization consider the DNS sub domain i=
nfrastructure, for a smaller organization consider SIEM events that stamp t=
he closest proximity security infrastructure into an event (zone based), ot=
hers might be ARP cache, DNS cache, etc.

b.      Role - compare with external maps to identify external facing endpo=
ints, fingerprint web server packages with a local agent, scrape local proc=
ess table to gauge TCP connections to the web server (is it really a web se=
rver), etc.

c.       Criticality - analytics on logins, active sessions, user account c=
ounts and net flow will provide a strong enterprise criticality score



4.       5.1 If the authenticated or unauthenticated data sets do get merge=
d or compared, a decision tree will have to be pre-established - does the a=
uthenticated/agent based score override a more recent  but unauthenticated =
scan finding?


5.       For Appendix B: Priority should include cyber intelligence and cam=
paign based vulnerability scores. For example, in 2013 - CVE's leveraged by=
 the "Red October Advanced Cyber Espionage Campaign targeting Diplomatic of=
ficials" should be prioritized well above the CVE's used in Conficker , etc=
. How can this standard be directed or modified to accept industry standard=
 Indicator of Compromise (IOC)'s and provide intel driven posture assessmen=
ts?



6.       Other general comments:



o   Are mutex string acquisition, DLL fingerprinting, IOC processing and au=
to remediation out of the scope for the current Working Group?  In addition=
, to Vulnerability assessment, these would all go nicely together as part o=
f a standard endpoint spec for vendors to communicate through.  I've seen e=
mail traffic from the group on several of these related topics.



o   Section 3. The multiple references to CMDB make some potential assumpti=
ons about managed vs. unmanaged endpoints

?  It's possible that unmanaged endpoints won't be found in a CMDB, does th=
is model account in any way for those?

?  An alternative is to consider continuous netflow analytics updating a re=
pository / data lake

o   Is Rogue Device Detection under consideration as a data point or even a=
n Endpoint Type?

o   Discovering neighboring endpoints

o   ARP as sensor data

o   Once a rogue device has been detected, a detailed (or secondary) vulner=
ability assessment should begin automatically.

Hope this helps.

Josh Stevens
Hewlett Packard Enterprise

From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, November 19, 2015 7:51 AM
To: opsec@ietf.org; opsawg@ietf.org
Cc: sacm@ietf.org
Subject: [sacm] Feedback on the SACM Vulnerability Assessment Scenario

Hi,

I am reiterating a request that I made at IETF 94 in the OPSAWG meeting, an=
d also sent to the mail lists of opsec and opsawg. The SACM WG is consideri=
ng a document https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scena=
rio/ that describes the operational practice of vulnerability reports, whic=
h we believe is an important use case in the security assessment life cycle=
. We are requiring feedback from operators about the scenario describe in t=
his document - does it make sense? Is it similar with what you do in operat=
ional real life? Are you using similar or different methods for vulnerabili=
ty assessment in your networks? A quick reading and short feedback would be=
 greatly appreciated.

Thanks and Regards,

Dan


--_000_9DDB58C939D0974CAEB9F2A0A0FC15C109DD9470G2W2529americas_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:64184420;
	mso-list-type:hybrid;
	mso-list-template-ids:1427785332 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:116797939;
	mso-list-type:hybrid;
	mso-list-template-ids:-959784644 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:124088049;
	mso-list-type:hybrid;
	mso-list-template-ids:-829128410 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3
	{mso-list-id:362707743;
	mso-list-type:hybrid;
	mso-list-template-ids:1651806646 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l3:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l4
	{mso-list-id:383024392;
	mso-list-type:hybrid;
	mso-list-template-ids:-1403118824 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l4:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l4:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l4:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l5
	{mso-list-id:481505207;
	mso-list-type:hybrid;
	mso-list-template-ids:2114338066 67698709 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l5:level1
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l5:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l5:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l6
	{mso-list-id:559023113;
	mso-list-type:hybrid;
	mso-list-template-ids:478200798 67698689 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l6:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l6:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l6:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l6:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l6:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l6:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l6:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l6:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l6:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l7
	{mso-list-id:606501634;
	mso-list-type:hybrid;
	mso-list-template-ids:-1571100518 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l7:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l7:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l7:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l7:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l8
	{mso-list-id:659700432;
	mso-list-type:hybrid;
	mso-list-template-ids:28712080 67698689 67698691 67698693 67698689 6769869=
1 67698693 67698689 67698691 67698693;}
@list l8:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l8:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l8:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l8:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l8:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l8:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l8:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l8:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l8:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l9
	{mso-list-id:723873139;
	mso-list-template-ids:1535013704;}
@list l9:level1
	{mso-level-start-at:3;
	mso-level-text:%1;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l9:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l9:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l9:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l9:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.75in;}
@list l9:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.75in;}
@list l9:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l9:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l9:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-1.25in;}
@list l10
	{mso-list-id:901675651;
	mso-list-type:hybrid;
	mso-list-template-ids:-1403118824 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l10:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l10:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l10:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l10:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l10:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l10:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l10:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l10:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l10:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l11
	{mso-list-id:944310388;
	mso-list-type:hybrid;
	mso-list-template-ids:-372460336 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l11:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l11:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l11:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l11:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l11:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l11:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l11:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l11:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l11:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l12
	{mso-list-id:1347246217;
	mso-list-type:hybrid;
	mso-list-template-ids:1651806646 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l12:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l12:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l12:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l12:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l12:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l12:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l12:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l12:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l12:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l13
	{mso-list-id:1410496063;
	mso-list-type:hybrid;
	mso-list-template-ids:759188410 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l13:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l13:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l13:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l13:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l13:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l13:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l13:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l13:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l13:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l14
	{mso-list-id:1441291456;
	mso-list-type:hybrid;
	mso-list-template-ids:157975182 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l14:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l14:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l14:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l14:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l14:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l14:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l14:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l14:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l14:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l15
	{mso-list-id:1720087612;
	mso-list-template-ids:-482605794;}
@list l15:level1
	{mso-level-start-at:3;
	mso-level-text:%1;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l15:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l15:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l15:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l15:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.75in;}
@list l15:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.75in;}
@list l15:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l15:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l15:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-1.25in;}
@list l16
	{mso-list-id:1844936066;
	mso-list-type:hybrid;
	mso-list-template-ids:1651806646 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l16:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l16:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l16:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l16:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l16:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l16:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l16:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l16:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l16:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l17
	{mso-list-id:1899978860;
	mso-list-type:hybrid;
	mso-list-template-ids:659737578 1608407992 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l17:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;}
@list l17:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;}
@list l17:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:1.75in;
	text-indent:-9.0pt;}
@list l17:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;}
@list l17:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;}
@list l17:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:3.25in;
	text-indent:-9.0pt;}
@list l17:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;}
@list l17:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;}
@list l17:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:4.75in;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Dan, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Agreed, this does help focus the work for this SACM =
Working Group. &nbsp;After reading the draft-coffin-sacm-vuln-scenario, I h=
ad some initial feedback from an enterprise defense perspective that might =
be incorporated.&nbsp; Here are my contributions:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l14 level1 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>In the abstract, a vulnerability report is referenc=
ed, however it&#8217;s not clear whether an authenticated or unauthenticate=
d vulnerability scan report (or both) is being referred to. &nbsp;If it can=
 consume both, I would call that out. If what&#8217;s
 being referred to is actually a recurring industry standard vulnerability =
report from a vendor, that could also clear up the abstract prior to the sc=
ope statement where the vulnerability report is defined.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l14 level1 lfo15;text-autospace:none">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>In the abstract, there isn&#8217;t a reference to t=
he endpoint based approach that is detailed in the next section. Ideally, i=
nstead of &#8220;It begins with an enterprise ingesting a vulnerability rep=
ort and ends at the point of identifying affected
 endpoints&#8221;,&nbsp; this could be better summarized as &#8220;Endpoint=
 data is pushed to a central point for comparison with vulnerability criter=
ia to enable posture assessment.&#8221; &nbsp;<o:p></o:p></p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l14 level1 lfo15;text-autospace:none">
<![if !supportLists]><span style=3D"mso-list:Ignore">3.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>3.3 A few comments on page 7, paragraph 4 &nbsp;&#8=
220;<span style=3D"font-size:10.0pt;font-family:Courier">The attributes cou=
ld be manually entered into a CMDB by a human, This would include any attri=
butes that cannot be collected programmatically.&#8221;</span>
 I believe the intent here is to leave fields open for the user to define a=
nd leverage as needed, however I'm not sure we want to advocate manual entr=
y? Ideally, if we can use a common set of algorithms that can be *manually*=
 adjusted to provide exception based
 rules to the overall effort.&nbsp; If we give a user the chance to mangle =
data sets, they probably will - I'm in favor of providing additional fields=
 that can be interfaced with other security API's where automation is the d=
efault workflow choice.&nbsp; &nbsp;Here are some
 alternatives to manual entry for these three categories: <o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.0in;text-indent:-.25in;mso=
-list:l14 level2 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">a.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Location - for a global organization consider the D=
NS sub domain infrastructure, for a smaller organization consider SIEM even=
ts that stamp the closest proximity security infrastructure into an event (=
zone based), others might be ARP
 cache, DNS cache, etc. <o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.0in;text-indent:-.25in;mso=
-list:l14 level2 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">b.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Role - compare with external maps to identify exter=
nal facing endpoints, fingerprint web server packages with a local agent, s=
crape local process table to gauge TCP connections to the web server (is it=
 really a web server), etc.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.0in;text-indent:-.25in;mso=
-list:l14 level2 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">c.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Criticality - analytics on logins, active sessions,=
 user account counts and net flow will provide a strong enterprise critical=
ity score
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l14 level1 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">4.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>5.1 If the authenticated or unauthenticated data se=
ts do get merged or compared, a decision tree will have to be pre-establish=
ed - does the authenticated/agent based score override a more recent&nbsp; =
but unauthenticated scan finding?
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l14 level1 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">5.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>For Appendix B: Priority should include cyber intel=
ligence and campaign based vulnerability scores. For example, in 2013 - CVE=
's leveraged by the &quot;Red October Advanced Cyber Espionage Campaign tar=
geting Diplomatic officials&quot; should be
 prioritized well above the CVE's used in Conficker , etc. How can this sta=
ndard be directed or modified to accept industry standard Indicator of Comp=
romise (IOC)&#8217;s and provide intel driven posture assessments?
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l14 level1 lfo15">
<![if !supportLists]><span style=3D"mso-list:Ignore">6.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Other general comments: <o:p></o:p></p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.0in;text-indent:-.25in;mso=
-list:l6 level2 lfo18">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>Are mutex string acquisition, DLL fingerprin=
ting, IOC processing and auto remediation out of the scope for the current =
Working Group? &nbsp;In addition, to Vulnerability assessment, these would =
all go nicely together as part of a standard
 endpoint spec for vendors to communicate through. &nbsp;I&#8217;ve seen em=
ail traffic from the group on several of these related topics.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.0in;text-indent:-.25in;mso=
-list:l6 level2 lfo18">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>Section 3. The multiple references to CMDB m=
ake some potential assumptions about managed vs. unmanaged endpoints<o:p></=
o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.5in;text-indent:-.25in;mso=
-list:l6 level3 lfo18">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">&sect;<span style=3D"font:7.0pt &quot;Times New Roman&quot;=
">&nbsp;
</span></span></span><![endif]>It&#8217;s possible that unmanaged endpoints=
 won't be found in a CMDB, does this model account in any way for those?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.5in;text-indent:-.25in;mso=
-list:l6 level3 lfo18">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">&sect;<span style=3D"font:7.0pt &quot;Times New Roman&quot;=
">&nbsp;
</span></span></span><![endif]>An alternative is to consider continuous net=
flow analytics updating a repository / data lake<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.0in;text-indent:-.25in;mso=
-list:l6 level2 lfo18">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>Is Rogue Device Detection under consideratio=
n as a data point or even an Endpoint Type?<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.25in;text-indent:-.25in;ms=
o-list:l6 level2 lfo18">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>Discovering neighboring endpoints<o:p></o:p>=
</p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.25in;text-indent:-.25in;ms=
o-list:l6 level2 lfo18">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>ARP as sensor data&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:1.25in;text-indent:-.25in;ms=
o-list:l6 level2 lfo18">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>Once a rogue device has been detected, a det=
ailed (or secondary) vulnerability assessment should begin automatically.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hope this helps. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Josh Stevens<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Hewlett Packard Enterprise <span style=3D"color:#1F4=
97D"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> sacm [mailto:sacm-bounces@ietf.org] <b>=
On Behalf Of
</b>Romascanu, Dan (Dan)<br>
<b>Sent:</b> Thursday, November 19, 2015 7:51 AM<br>
<b>To:</b> opsec@ietf.org; opsawg@ietf.org<br>
<b>Cc:</b> sacm@ietf.org<br>
<b>Subject:</b> [sacm] Feedback on the SACM Vulnerability Assessment Scenar=
io<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am reiterating a request that I made at IETF 94 in=
 the OPSAWG meeting, and also sent to the mail lists of opsec and opsawg. T=
he SACM WG is considering a document
<a href=3D"https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario=
/">https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/</a> th=
at describes the operational practice of vulnerability reports, which we be=
lieve is an important use case in
 the security assessment life cycle. We are requiring feedback from operato=
rs about the scenario describe in this document &#8211; does it make sense?=
 Is it similar with what you do in operational real life? Are you using sim=
ilar or different methods for vulnerability
 assessment in your networks? A quick reading and short feedback would be g=
reatly appreciated.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9DDB58C939D0974CAEB9F2A0A0FC15C109DD9470G2W2529americas_--


From nobody Sun Nov 22 06:48:16 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A4B1A8981; Sun, 22 Nov 2015 06:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.095
X-Spam-Level: 
X-Spam-Status: No, score=-4.095 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585] autolearn=ham
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 bJ_hC93N9ELs; Sun, 22 Nov 2015 06:48:11 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 958871A8993; Sun, 22 Nov 2015 06:48:11 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AWAgBA1VFW/xUHmMZeGQEBAQEPAQEBAYI+ISxTbwaEI4EPtz+CGgENgWUghW8CgSI4FAEBAQEBAQGBCoQ0AQEBAQMSCxBMEAIBCA0EBAEBCx0HMhQJCAIEAQ0FCBEJiAwBDKNxmiYBAQEBAQEBAQEBAQEBAQEBAQEBAQEUBIZWhHyEOwEBHi0JgxOBFQWWUAGFI4loh1kMjxmDch8BAUKBYCyBeHIBAYNoOgGBBgEBAQ
X-IPAS-Result: A2AWAgBA1VFW/xUHmMZeGQEBAQEPAQEBAYI+ISxTbwaEI4EPtz+CGgENgWUghW8CgSI4FAEBAQEBAQGBCoQ0AQEBAQMSCxBMEAIBCA0EBAEBCx0HMhQJCAIEAQ0FCBEJiAwBDKNxmiYBAQEBAQEBAQEBAQEBAQEBAQEBAQEUBIZWhHyEOwEBHi0JgxOBFQWWUAGFI4loh1kMjxmDch8BAUKBYCyBeHIBAYNoOgGBBgEBAQ
X-IronPort-AV: E=Sophos;i="5.20,332,1444708800";  d="scan'208,217";a="147177792"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Nov 2015 09:48:10 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 22 Nov 2015 09:48:09 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Sun, 22 Nov 2015 09:48:08 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "opsec@ietf.org" <opsec@ietf.org>,  "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [sacm] [OPSAWG] Feedback on the SACM Vulnerability Assessment Scenario
Thread-Index: AQHRIwn8vCnc3ktnmEWoJx2rPsfBeZ6n9pzA
Date: Sun, 22 Nov 2015 14:48:07 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BEA384A@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA6BE9F6C7@AZ-FFEXMB04.global.avaya.com> <4A95BA014132FF49AE685FAB4B9F17F657DA3D4B@dfweml701-chm>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F657DA3D4B@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA6BEA384AAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/yfIZWj1BMUqzkIWozB5OKZBrJLw>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [OPSAWG] [sacm] Feedback on the SACM Vulnerability Assessment Scenario
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Nov 2015 14:48:14 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA6BEA384AAZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Linda,

Thanks for answering the call for review and having a look at this work.

Concerning your 'little disappointment': This I-D needs to be read in the c=
ontext of the current charter of the SACM WG. The WG charter focus for this=
 phase is on the 'endpoint posture' and on the 'enterprise use case'. Maybe=
 this makes things somehow more clear.

Regards,

Dan


From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Linda Dunbar
Sent: Thursday, November 19, 2015 10:36 PM
To: Romascanu, Dan (Dan); opsec@ietf.org; opsawg@ietf.org
Cc: sacm@ietf.org
Subject: Re: [sacm] [OPSAWG] Feedback on the SACM Vulnerability Assessment =
Scenario

Reading through the document has made me feel that the Title of the draft i=
s misleading.
Based on the title I was expecting to see the Vulnerability Assessment of v=
arious network scenarios, which will be very useful information for enterpr=
ise and service provider network administrators to put in adequate tools to=
 protect those vulnerability.

But the document only describes the procedure in authenticating a end user/=
points and states that you need to compare with the Vulnerability report (a=
lmost like a common sense ) without saying how and what.  I guess I had too=
 high the expectation, but a little disappointed of not finding the informa=
tion I was looking for.

Linda Dunbar



From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Romascanu, Dan (=
Dan)
Sent: Thursday, November 19, 2015 7:51 AM
To: opsec@ietf.org<mailto:opsec@ietf.org>; opsawg@ietf.org<mailto:opsawg@ie=
tf.org>
Cc: sacm@ietf.org<mailto:sacm@ietf.org>
Subject: [OPSAWG] Feedback on the SACM Vulnerability Assessment Scenario

Hi,

I am reiterating a request that I made at IETF 94 in the OPSAWG meeting, an=
d also sent to the mail lists of opsec and opsawg. The SACM WG is consideri=
ng a document https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scena=
rio/<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.iet=
f.org_doc_draft-2Dcoffin-2Dsacm-2Dvuln-2Dscenario_&d=3DBQMFAg&c=3DBFpWQw8bs=
uKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DDXOABUhWg=
QkWYGVviFzuEvwgbivmgrBaeyHQ3_W-Hyg&s=3DS_CieVlne2x4XqE2cNL0Y_mb0dcPAGm4cN6h=
Ka5k-6Q&e=3D> that describes the operational practice of vulnerability repo=
rts, which we believe is an important use case in the security assessment l=
ife cycle. We are requiring feedback from operators about the scenario desc=
ribe in this document - does it make sense? Is it similar with what you do =
in operational real life? Are you using similar or different methods for vu=
lnerability assessment in your networks? A quick reading and short feedback=
 would be greatly appreciated.

Thanks and Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA6BEA384AAZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Linda, <o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for answering t=
he call for review and having a look at this work.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Concerning your &#8216=
;little disappointment&#8217;: This I-D needs to be read in the context of =
the current charter of the SACM WG. The WG charter focus for this phase is =
on the &#8216;endpoint posture&#8217; and on the &#8216;enterprise
 use case&#8217;. Maybe this makes things somehow more clear. <o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dan<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sacm [ma=
ilto:sacm-bounces@ietf.org]
<b>On Behalf Of </b>Linda Dunbar<br>
<b>Sent:</b> Thursday, November 19, 2015 10:36 PM<br>
<b>To:</b> Romascanu, Dan (Dan); opsec@ietf.org; opsawg@ietf.org<br>
<b>Cc:</b> sacm@ietf.org<br>
<b>Subject:</b> Re: [sacm] [OPSAWG] Feedback on the SACM Vulnerability Asse=
ssment Scenario<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Reading through the do=
cument has made me feel that the Title of the draft is misleading.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Based on the title I w=
as expecting to see the Vulnerability Assessment of various network scenari=
os, which will be very useful information for enterprise and service provid=
er network administrators to put in
 adequate tools to protect those vulnerability. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">But the document only =
describes the procedure in authenticating a end user/points and states that=
 you need to compare with the Vulnerability report (almost like a common se=
nse ) without saying how and what. &nbsp;I
 guess I had too high the expectation, but a little disappointed of not fin=
ding the information I was looking for.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Linda Dunbar<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> OPSAWG [=
<a href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.org</=
a>]
<b>On Behalf Of </b>Romascanu, Dan (Dan)<br>
<b>Sent:</b> Thursday, November 19, 2015 7:51 AM<br>
<b>To:</b> <a href=3D"mailto:opsec@ietf.org">opsec@ietf.org</a>; <a href=3D=
"mailto:opsawg@ietf.org">
opsawg@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
<b>Subject:</b> [OPSAWG] Feedback on the SACM Vulnerability Assessment Scen=
ario<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am reiterating a request that I made at IETF 94 in=
 the OPSAWG meeting, and also sent to the mail lists of opsec and opsawg. T=
he SACM WG is considering a document
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatrack=
er.ietf.org_doc_draft-2Dcoffin-2Dsacm-2Dvuln-2Dscenario_&amp;d=3DBQMFAg&amp=
;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphp=
BsFA&amp;m=3DDXOABUhWgQkWYGVviFzuEvwgbivmgrBaeyHQ3_W-Hyg&amp;s=3DS_CieVlne2=
x4XqE2cNL0Y_mb0dcPAGm4cN6hKa5k-6Q&amp;e=3D">
https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/</a> that =
describes the operational practice of vulnerability reports, which we belie=
ve is an important use case in the security assessment life cycle. We are r=
equiring feedback from operators
 about the scenario describe in this document &#8211; does it make sense? I=
s it similar with what you do in operational real life? Are you using simil=
ar or different methods for vulnerability assessment in your networks? A qu=
ick reading and short feedback would be
 greatly appreciated. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA6BEA384AAZFFEXMB04globa_--


From nobody Sun Nov 22 11:39:29 2015
Return-Path: <jclarke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E66A1B2A36 for <opsawg@ietfa.amsl.com>; Sun, 22 Nov 2015 11:39:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level: 
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 vCaEwepLxgcu for <opsawg@ietfa.amsl.com>; Sun, 22 Nov 2015 11:39:25 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A2171B29FA for <opsawg@ietf.org>; Sun, 22 Nov 2015 11:39:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=463; q=dns/txt; s=iport; t=1448221165; x=1449430765; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=LPjhQcUvrsJb3kBnvtJJpMN2dry/Nmqko1ODgtheHvU=; b=VS2nwoIIjipcqjy4vREsPHJhlUHIwCI5RWExJDWbz8568gngvPrdIRGZ ibXyZCchWl23r807Ggkd5igtp9Fq9PPZfcJWxNigBJKCNuTj8Ut93ysvd QZggHpZbsLpAuoyu3+aKdjqFp0kbl12XjkAIyaZbCqflLwqifuw4FDmA7 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DzAQAfGVJW/5FdJa1egzvAVAENgWWGB?= =?us-ascii?q?YEuOBQBAQEBAQEBfwuEXhVANgIFFgsCCwMCAQIBSw0IAQGIKp5Oj3CPRAEBAQE?= =?us-ascii?q?GAQEBAR+BAYVThj6GNYFEBY4UiDyNMYkdhiaNCB8BAUKCHoIEIIVfAQEB?=
X-IronPort-AV: E=Sophos;i="5.20,333,1444694400"; d="scan'208";a="47087980"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Nov 2015 19:39:24 +0000
Received: from [10.117.46.173] (rtp-jclarke-89112.cisco.com [10.117.46.173]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id tAMJdOGD019317 for <opsawg@ietf.org>; Sun, 22 Nov 2015 19:39:24 GMT
To: "opsawg@ietf.org" <opsawg@ietf.org>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
Message-ID: <565219EC.1080007@cisco.com>
Date: Sun, 22 Nov 2015 14:39:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ZyyprNdTQBQ8L7xPJkS8Xd223Z4>
Subject: [OPSAWG] Implementation of RFC7630
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Nov 2015 19:39:26 -0000

I was getting some questions from internal parties regarding the 
implementation of SHA-2 authn for SNMPv3, and wanted to check the list 
to gage what NMS vendors and operators might be considering with respect 
to this.  Is there a strong desire among operators to move to adopt 
SHA-2?  Are those operators already using SNMPv3 or would this provide 
the necessary push to move to v3?  Are there NMS applications already 
adopting SHA-2?  Thanks.

Joe


From nobody Sun Nov 22 12:45:12 2015
Return-Path: <joelja@bogus.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 097701B34C0 for <opsawg@ietfa.amsl.com>; Sun, 22 Nov 2015 12:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585] autolearn=ham
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 ULpRMc85a09Z for <opsawg@ietfa.amsl.com>; Sun, 22 Nov 2015 12:45:08 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2C6A1B34BF for <opsawg@ietf.org>; Sun, 22 Nov 2015 12:45:08 -0800 (PST)
Received: from mb-2.local ([IPv6:2601:1c0:c102:22fb:dcd6:8d20:dc38:5fb4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id tAMKj5BU073170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 22 Nov 2015 20:45:06 GMT (envelope-from joelja@bogus.com)
To: Joe Clarke <jclarke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <565219EC.1080007@cisco.com>
From: joel jaeggli <joelja@bogus.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56522951.8010807@bogus.com>
Date: Sun, 22 Nov 2015 12:45:05 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Thunderbird/42.0
MIME-Version: 1.0
In-Reply-To: <565219EC.1080007@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6a1mLgXKcaHBm7X6L1beXD3iVpjmnD4Gk"
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/Yxlw-fHjYG6AeXHjVoJrrps61-4>
Subject: Re: [OPSAWG] Implementation of RFC7630
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Nov 2015 20:45:10 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6a1mLgXKcaHBm7X6L1beXD3iVpjmnD4Gk
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 11/22/15 11:39 AM, Joe Clarke wrote:
> I was getting some questions from internal parties regarding the
> implementation of SHA-2 authn for SNMPv3, and wanted to check the list
> to gage what NMS vendors and operators might be considering with respec=
t
> to this.  Is there a strong desire among operators to move to adopt
> SHA-2?  Are those operators already using SNMPv3 or would this provide
> the necessary push to move to v3?  Are there NMS applications already
> adopting SHA-2?  Thanks.

We use SHA and AES with snmp v3. Given the general pressue other parts
of the business to carefully track and generally improve which crypto
suites are used we would probably move there if the hardware supported
it (I don't think getting it done in the NMS would really be that hard).
To the extent that I had an auditor ask about it, it's been a while, but
md5 and des was the topic of conversation at that time.

> Joe
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20



--6a1mLgXKcaHBm7X6L1beXD3iVpjmnD4Gk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlZSKVEACgkQ8AA1q7Z/VrLGtgCfYbu+TwWrCgOJ3ChbffuKDtzh
Q9kAn1CmcEW+H1HIwzv5PYoeFMJrUViK
=V/+5
-----END PGP SIGNATURE-----

--6a1mLgXKcaHBm7X6L1beXD3iVpjmnD4Gk--


From nobody Sun Nov 22 18:35:39 2015
Return-Path: <randy@psg.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C920B1B2E1C for <opsawg@ietfa.amsl.com>; Sun, 22 Nov 2015 18:35:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585] autolearn=ham
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 y-ZN7fb5GAtS for <opsawg@ietfa.amsl.com>; Sun, 22 Nov 2015 18:35:38 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEC9F1B2E1B for <opsawg@ietf.org>; Sun, 22 Nov 2015 18:35:37 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1a0gyd-0004gC-QX; Mon, 23 Nov 2015 02:35:35 +0000
Date: Mon, 23 Nov 2015 03:35:31 +0100
Message-ID: <m2d1v1v3ws.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: joel jaeggli <joelja@bogus.com>
In-Reply-To: <56522951.8010807@bogus.com>
References: <565219EC.1080007@cisco.com> <56522951.8010807@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ALXDc4YM8nWwUomcvVDsvKrXaFM>
Cc: opsawg <opsawg@ietf.org>
Subject: Re: [OPSAWG] Implementation of RFC7630
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 02:35:39 -0000

> We use SHA and AES with snmp v3. Given the general pressue other parts
> of the business to carefully track and generally improve which crypto
> suites are used we would probably move there if the hardware supported
> it (I don't think getting it done in the NMS would really be that
> hard).

not a hot button, but on the gonna-have-to-do-in-the-next-year-or-three
list.

randy


From nobody Mon Nov 23 08:09:41 2015
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB6C1A897F for <opsawg@ietfa.amsl.com>; Mon, 23 Nov 2015 08:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
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 EJZSruuG_D2Z for <opsawg@ietfa.amsl.com>; Mon, 23 Nov 2015 08:09:39 -0800 (PST)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (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 EAED91A897C for <opsawg@ietf.org>; Mon, 23 Nov 2015 08:09:38 -0800 (PST)
Received: by ykfs79 with SMTP id s79so243649583ykf.1 for <opsawg@ietf.org>; Mon, 23 Nov 2015 08:09:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=04Y7js9idOzuziTRL33nH7fCGtCBygU9XHIaGeRJwJg=; b=GApp1MjabBukhNsB9HqVU+BtItn61TgGRa8ctWNod5jUyvD9IUSdjLlSCwMMyIPLVa OJhb2Rf0DPoTtqSt9ca/XXXbRZOz31eU6Q816gdM89k6AK2OAMCNQi2hZLPIMCjsIkGv AlfK3J7pWoQZ/bNOcOHEDubeuOeHBaUxcgRDpX9v5sTMOGqOmPepmcUgaXnQoC72bMnT RGFySrE7RbypxB5Kkw0YXUmfH77H5+UMb2+0q6Gwz8nAbuxeS6DwCbZeECQpF5+7PlhB Bp6vaPxN+wlKwsSUhmZ4zdpNRq0/w69P48S6zSIf2ZR2XBrfF4OsCE+nSfJAw7jDpfDa EOGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=04Y7js9idOzuziTRL33nH7fCGtCBygU9XHIaGeRJwJg=; b=NkQSFmKppFf9iBR3eMaIk4I5XD8lAWSFd5g5CeFwZoTGO0uYFL5ZYidXJ/3x08tT15 qkRAeA1NxknyzvxWfPEEYC/CNko7pOrZjXW9+8z84u3glmPwsSDojl3yu0IJo0QTrl0f R1YLqAlCSer/J8/FMXXCU8eoh2OaRACah+JH11lag8vuVh5IEKxvgTprJhVL91wgT9qv rJeWBMr4+X5y31liWY0WQFIUWrUd9UlUhUaGEfm1Rl9GnLQ6CO7ivjcprQmBGOP1d4D1 hJYvrchyqoKyTKmHAHW/v7MCsH2DBKX2iwhkWuzOt06MaGsavhV4H1uZwg91KBc+hypN G9VQ==
X-Gm-Message-State: ALoCoQnY3/GTfoSdizG0sAfnQalt7OrBh4cAIyrXhiYq9fHhhqOeZY/u4BC9DFSuufs6o/kpHh4x
X-Received: by 10.129.93.133 with SMTP id r127mr23918397ywb.109.1448294977776;  Mon, 23 Nov 2015 08:09:37 -0800 (PST)
MIME-Version: 1.0
References: <565219EC.1080007@cisco.com> <56522951.8010807@bogus.com> <m2d1v1v3ws.wl%randy@psg.com>
In-Reply-To: <m2d1v1v3ws.wl%randy@psg.com>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 23 Nov 2015 16:09:28 +0000
Message-ID: <CAHw9_iKxxyOgWd1NG6hQJfJqGjrWHCNeT-D1AkRP5j_cEUUrQQ@mail.gmail.com>
To: Randy Bush <randy@psg.com>, joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=001a114d8bc6ae53b70525377301
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/C3lt5cfnFKIP90x6vGzI_PgUGgo>
Cc: opsawg <opsawg@ietf.org>
Subject: Re: [OPSAWG] Implementation of RFC7630
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 16:09:40 -0000

--001a114d8bc6ae53b70525377301
Content-Type: text/plain; charset=UTF-8

People seem to be beginning to get on the "SHA-1 is dead" bandwagon, and
are increasingly moving along the "Whoa, MD5, that's *so* 2010" -- so,
yeah, I'd agree with Randy on the "next year or three".
W

On Sun, Nov 22, 2015 at 9:35 PM Randy Bush <randy@psg.com> wrote:

> > We use SHA and AES with snmp v3. Given the general pressue other parts
> > of the business to carefully track and generally improve which crypto
> > suites are used we would probably move there if the hardware supported
> > it (I don't think getting it done in the NMS would really be that
> > hard).
>
> not a hot button, but on the gonna-have-to-do-in-the-next-year-or-three
> list.
>
> randy
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

--001a114d8bc6ae53b70525377301
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">People seem to be beginning to get on the &quot;SHA-1 is d=
ead&quot; bandwagon, and are increasingly moving along the &quot;Whoa, MD5,=
 that&#39;s *so* 2010&quot; -- so, yeah, I&#39;d agree with Randy on the &q=
uot;next year or three&quot;.<div>W</div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr">On Sun, Nov 22, 2015 at 9:35 PM Randy Bush &lt;<a href=
=3D"mailto:randy@psg.com">randy@psg.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">&gt; We use SHA and AES with snmp v3. Given the general=
 pressue other parts<br>
&gt; of the business to carefully track and generally improve which crypto<=
br>
&gt; suites are used we would probably move there if the hardware supported=
<br>
&gt; it (I don&#39;t think getting it done in the NMS would really be that<=
br>
&gt; hard).<br>
<br>
not a hot button, but on the gonna-have-to-do-in-the-next-year-or-three<br>
list.<br>
<br>
randy<br>
<br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org" target=3D"_blank">OPSAWG@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</blockquote></div>

--001a114d8bc6ae53b70525377301--


From nobody Mon Nov 23 08:24:30 2015
Return-Path: <prvs=87696b30a5=uri@ll.mit.edu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29CF91A8A1D for <opsawg@ietfa.amsl.com>; Mon, 23 Nov 2015 08:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.783
X-Spam-Level: 
X-Spam-Status: No, score=-4.783 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 QTQrTbuWVZSB for <opsawg@ietfa.amsl.com>; Mon, 23 Nov 2015 08:24:26 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 90A271A8A1B for <opsawg@ietf.org>; Mon, 23 Nov 2015 08:24:26 -0800 (PST)
Received: from LLE2K10-HUB02.mitll.ad.local (LLE2K10-HUB02.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tANGOH17028410; Mon, 23 Nov 2015 11:24:17 -0500
From: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
To: joel jaeggli <joelja@bogus.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Implementation of RFC7630
Thread-Index: AQHRJV2G7ZRBQM60F0ehM8mNx80DtJ6o1muAgAD1lYA=
Date: Mon, 23 Nov 2015 16:24:17 +0000
Message-ID: <D278A6D1.22D89%uri@ll.mit.edu>
References: <565219EC.1080007@cisco.com> <56522951.8010807@bogus.com>
In-Reply-To: <56522951.8010807@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-originating-ip: [172.25.177.187]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3531122643_102934371"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-11-23_08:2015-11-23,2015-11-23,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1511230282
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/gmKlwq_j83LE6ApyWrNdoIcZdks>
Subject: Re: [OPSAWG] Implementation of RFC7630
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 16:24:29 -0000

--B_3531122643_102934371
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

On 11/22/15, 15:45 , "OPSAWG on behalf of joel jaeggli"
<opsawg-bounces@ietf.org on behalf of joelja@bogus.com> wrote:

>On 11/22/15 11:39 AM, Joe Clarke wrote:
>> I was getting some questions from internal parties regarding the
>> implementation of SHA-2 authn for SNMPv3, and wanted to check the list
>> to gage what NMS vendors and operators might be considering with respect
>> to this.  Is there a strong desire among operators to move to adopt
>> SHA-2?  Are those operators already using SNMPv3 or would this provide
>> the necessary push to move to v3?  Are there NMS applications already
>> adopting SHA-2?  Thanks.
>
>We use SHA and AES with snmp v3. Given the general pressue other parts
>of the business to carefully track and generally improve which crypto
>suites are used we would probably move there if the hardware supported
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>it (I don't think getting it done in the NMS would really be that hard).
>To the extent that I had an auditor ask about it, it's been a while, but
>md5 and des was the topic of conversation at that time.

By =E2=80=9Chardware=E2=80=9D you probably mean =E2=80=9Cmanaged devices/managed agents=E2=80=9D? B=
ecause
I don=E2=80=99t think any general-purpose hardware (besides newer Intel CPUs)
supports it.

--B_3531122643_102934371
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQ0AYJKoZIhvcNAQcCoIIQwTCCEL0CAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGggg6fMIIE6jCCA9KgAwIBAgIKE5SxSwAAAABE8TANBgkqhkiG9w0BAQsFADBRMQswCQYD
VQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJ
MRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1MDYxNTE2MjQzOVoXDTE2MDYxNDE2MjQzOVow
YTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNV
BAsTBlBlb3BsZTEgMB4GA1UEAxMXQmx1bWVudGhhbC5VcmkuNTAwMTA1ODQwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQC0tVFZOYvbDipiXfjylg0yIORem8AMZ4UQJ7EM2BI8
jKLj/h3RwH4w2DOMdepALLUqscSrpX6HPbo80M1O0cSSIYcYl8wQzDAMmvoD3HWbupwSXEPf
eRtBo26jAvsDkOp46TPu40Pu61AkHx4vIgqU7XkofKhow18Ka/9ZkJ+oSnLK6Xy9+n8JiViO
kTm2NjyF+CcpAobwZ3lBepHihvK3EilYR6V1EHQb+Y+2aWtexkFzBNXaN7i4Sdzq+LNSzCON
DDDnRxA2c/B/p7MBDzocaigPxmKOHcE5eamxCgpJEUVCEALzeVZxcYURDJw68tZ90pJSLuw7
r6iigykQbRINAgMBAAGjggGyMIIBrjAdBgNVHQ4EFgQUQzxm8xAhtcoaGyRStaMMhrmd7/Mw
DgYDVR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1Ud
HwQsMCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYB
BQUHAQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExD
QTMwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3
FQcEMDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAi
BgNVHSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3
EgIBAwEIMBkGA1UdEQQSMBCBDnVyaUBsbC5taXQuZWR1MCcGCSsGAQQBgjcUAgQaHhgATABM
AFUAcwBlAHIAUwBpAGcALQBTAFcwDQYJKoZIhvcNAQELBQADggEBAI8vbC+RZJEH0jhe5e9w
F18xYCquDo5kxkoD83qYcVPVFYPnjuAvZ6o9ENa3F0GiAjFVm6HcUbm0zeWT6ZDYIrbh7GRM
4IO8pD9ziwvLIx8rvLvUhiBpsZvznVOWX1yGC0UkIKyiseAszczAYFVJonKB8jDRnxgFlPlo
mFUaDtjL86cyp+pHc+ffUVyqMxacABFutJJ72HcK7tIf2gnh2qLdKToiTkDIWT+b1RrkQPSr
Gr0YapAC5PgHd/RRY75FHdW/OEQOFimouKnBc5F2VsDJg0Ae9i0+nJPWwSpoXe0ISqIUMO47
Ei6ySfHR2mjymbByxmT5W3gAT3M2gyOd/XUwggS8MIIDpKADAgECAgEpMA0GCSqGSIb3DQEB
BQUAMFQxCzAJBgNVBAYTAlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQww
CgYDVQQLEwNQS0kxFjAUBgNVBAMTDU1JVExMIFJvb3QgQ0EwHhcNMTMxMjE3MDAwMDAwWhcN
MjAxMjMxMjM1OTU5WjBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFi
b3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2jBSdW18tuW1tNxG6h8B0kqckFZQAAtoHCkvUpUEX6jF
vBd8mQI53GyLYRuAo4HWJpe7/izFXOfSJDs6UM5ovvCOfXg2bJgDYlBC9JDcLBFIn0nppOu9
RvpjWSixtC56crwJ5Us5QPdtxtKdek5LJXl2oKw3w8lihUixePbxWad1m7ZMKKagvm9zTybP
6FumKRxeYJjSpB2+cAYjoGGEbSVHyx8uzHm6xAoBMHxa8by+yDz8Jzk6sP9iilgP3iXSGoCA
mhyBzvlQQ5QNNWP+Emo9jz/ukKhYVB/VwdxtoquPAqn4ifDAIaM9dtb05cy1gXAFSP3Z/iUk
xyBZZUORfwIDAQABo4IBmjCCAZYwEgYDVR0TAQH/BAgwBgEB/wIBADAdBgNVHQ4EFgQU12Bm
DntJjXVMDf3PRt7IxxKHyr8wHwYDVR0jBBgwFoAUZ6p6z/QKprlytYqg0p3yEMND7SkwDgYD
VR0PAQH/BAQDAgGGMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0cDovL2NybC5s
bC5taXQuZWR1L2dldHRvP0xMUkNBMCcGCCsGAQUFBzABhhtodHRwOi8vb2NzcC5sbC5taXQu
ZWR1L29jc3AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC5sbC5taXQuZWR1L2dldGNy
bD9MTFJDQTCBkgYDVR0gBIGKMIGHMA0GCyqGSIb3EgIBAwEGMA0GCyqGSIb3EgIBAwEIMA0G
CyqGSIb3EgIBAwEHMA0GCyqGSIb3EgIBAwEJMA0GCyqGSIb3EgIBAwEKMA0GCyqGSIb3EgIB
AwELMA0GCyqGSIb3EgIBAwEOMA0GCyqGSIb3EgIBAwEPMA0GCyqGSIb3EgIBAwEQMA0GCSqG
SIb3DQEBBQUAA4IBAQAsf9HBn72qU7UTgkxarjAc7iynhcDEgWwezYKtd/SLGSQ0DhtzIV/L
TCxqULjOd+H+HTqMJXB8+nHnzhyqQ43RsnGZOFT5RfzPh94db/ZJ3ql244DwlJI7yXBA2DkZ
cEEgOWC9bHcrElzU6NnigahSW5odVJrhmH/XhQAcMS77E5H62yyxK1WPPgcBipGVnu1xSHbT
iHe7DqfWQ2tVMLUf23XYhIua94kJsQd4jSh71NVD0e7F4snAoqQMI98MzDYeLOkjlzKRs77r
/aMsPAKx6nMaOvRL7Cy0Pjp51i2qFkbGmX8ofnh2kerjTTvRJ/g22r1MV8RR1PktjMsNOsPf
MIIE7TCCA9WgAwIBAgIKKHB6MgAAAAAtBzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJV
UzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYD
VQQDEwpNSVRMTCBDQS0zMB4XDTE1MDEyMzE3NDkyOVoXDTE2MDEyMzE3NDkyOVowYTELMAkG
A1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBl
b3BsZTEgMB4GA1UEAxMXQmx1bWVudGhhbC5VcmkuNTAwMTA1ODQwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQDF+Rcs9hNO5hvlE0YeltqeXGUW1u3RVMG4/2ag6J2FgcsOJxOZ
y/m+7FeYfCo3XYrNqx6/3IZmDSYln3JnxzPionDcbK2TJ9xAOoWlrUykAhgUl+PCO8ahDV5Y
c0tmMzf5MXBrsub0nUyJeDkxOUY2Id58D1UVzzXh9Kvjc+ZCcBRFoViAgn7MznnuvK8Y5m7L
or1oLWSxNNUyp98gC4EpdHLnA8yP1WqmNr0x+YssjJgEiIfZFqx8Gvv2OqtHaFGHh7Y6+WOW
IZULMaAc9JJEq8ctns9mGIRldf2JMFcNsahQJDhgUspmP6c1Wz9OrUxsgwnGQ5feIq9c/4YZ
YEZ/AgMBAAGjggG1MIIBsTAdBgNVHQ4EFgQUR0hebk4i6063YnpEEVXyQUyfSFMwDgYDVR0P
AQH/BAQDAgUgMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQsMCow
KKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUHAQEE
WjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMwJwYI
KwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcEMDAu
BiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2F69Bwg+vtIAIBZAIBBDAlBgNVHSUE
HjAcBgRVHSUABggrBgEFBQcDBAYKKwYBBAGCNwoDBDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMBkGA1UdEQQSMBCBDnVyaUBsbC5taXQuZWR1MCcGCSsGAQQBgjcUAgQaHhgATABMAFUA
cwBlAHIARQBuAGMALQBTAFcwDQYJKoZIhvcNAQELBQADggEBADim5zjTb/h3ea/66DNM6wSm
i1Ti9F2f2/Are2a7a9E/IPXfleh39lVG7uTaneEJMSHzDltkB5k6DYMv/t28ntQm2jLI9adM
wccDlKSR2uIDsiA7jodiTxbqL/aRi+WC4ybWWhXuzSbkMesayt5QAKpuKLAr7newfZaWx8zP
nWU1nWZBbJR7cLKgUTaEiQu/NlCWIFJIC9yRhze+KR41vIa+7niQnUANjoYCCu32Z8xgxhK4
kQr5teUVUNDoCj02x781GFfwCknxpsWEm95OWM1iaXKCGJ8ciioulEzksZUrIHdImISaQVV+
Xdmbcd3OH6y8fNl1mZdXn8sxNJc+/g0xggH1MIIB8QIBATBfMFExCzAJBgNVBAYTAlVTMR8w
HQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNVBAMT
Ck1JVExMIENBLTMCChOUsUsAAAAARPEwDQYJYIZIAWUDBAIBBQCgaTAvBgkqhkiG9w0BCQQx
IgQgo8O+pQUffbZMxjR53gnhenGzeLTk+Fbg2SVhOzUBJIYwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTUxMTIzMTYyNDAzWjANBgkqhkiG9w0BAQEFAASC
AQCcXUzoyIqFH2PInac0th+o+7qIAfx0HmN1JXxrPHnFWYzkEHpGGOwTVQZChm1E5TepADfh
e9mUbDu6/RL+vYqgk0iLtBkNJrGPhQdQTAI8H5EtEreEvRA9wtxca9c+bc5ItSJKevtOvjGC
Ixnge1aU9PatSJyDjGUg2xDThuK/+yWQhezPqpgheYFSTuAQZzIoTE4MsSiqMnfRqQ/FJQbd
XzLpauanSnsS0q3nEr8GEm8HEoXhnHu6330vS66+yOdyNrMSjvsHutirQBUcLy8/6UQlqr4H
EDJ4Lqmq1iwQdtsUcgZTiAqEBL8FTV+JZAdlDIHdqjGGl74p5zlRwrPs

--B_3531122643_102934371--


From nobody Mon Nov 23 08:51:59 2015
Return-Path: <reid@snmp.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401431A906A for <opsawg@ietfa.amsl.com>; Mon, 23 Nov 2015 08:51:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.588
X-Spam-Level: 
X-Spam-Status: No, score=-0.588 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 wNe529f92lEu for <opsawg@ietfa.amsl.com>; Mon, 23 Nov 2015 08:51:52 -0800 (PST)
Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8371A9067 for <opsawg@ietf.org>; Mon, 23 Nov 2015 08:51:49 -0800 (PST)
Received: from mainfs.snmp.com (mainfs.snmp.com [192.147.142.124]) by mailbox.snmp.com (8.9.3p2-20030922/m.0080228) with ESMTP id LAA08975; Mon, 23 Nov 2015 11:51:41 -0500 (EST)
Received: from mainfs.snmp.com (localhost [127.0.0.1]) by mainfs.snmp.com (8.14.5/8.14.5) with ESMTP id tANGpetg022920; Mon, 23 Nov 2015 11:51:40 -0500 (EST) (envelope-from reid@snmp.com)
Message-Id: <201511231651.tANGpetg022920@mainfs.snmp.com>
To: Joe Clarke <jclarke@cisco.com>
From: David Reid <reid@snmp.com>
In-reply-to: Your message of Sun, 22 Nov 2015 14:39:24 -0500. <565219EC.1080007@cisco.com>
Date: Mon, 23 Nov 2015 11:51:40 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/D2Xq_m2yrpkaAOwdV-NwfpWxNkw>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Implementation of RFC7630
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Reid <reid@snmp.com>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 16:51:58 -0000

> I was getting some questions from internal parties regarding the 
> implementation of SHA-2 authn for SNMPv3, and wanted to check the list 
> to gage what NMS vendors and operators might be considering with respect 
> to this.  Is there a strong desire among operators to move to adopt 
> SHA-2?  Are those operators already using SNMPv3 or would this provide 
> the necessary push to move to v3?  Are there NMS applications already 
> adopting SHA-2?  Thanks.

SHA-2 is available today with CA's eHealth and HP's OVPI. Both of these
NMS applications get SNMPv3 support through a 3rd party add-on from
SNMP Research called the Distributed SNMP Security Pack (DSSP) which 
supports SHA-2 as an optional feature. DSSP can be made to work with 
other NMSs as well.  The SNMP manager and agent toolkits from SNMP 
Research also support SHA-2.

-David Reid


From nobody Fri Nov 27 03:33:07 2015
Return-Path: <dcmgash@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9741B32C1 for <opsawg@ietfa.amsl.com>; Fri, 27 Nov 2015 03:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level: 
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 2goXa0prs0p7 for <opsawg@ietfa.amsl.com>; Fri, 27 Nov 2015 03:33:04 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03FBA1B32C0 for <opsawg@ietf.org>; Fri, 27 Nov 2015 03:33:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4610; q=dns/txt; s=iport; t=1448623984; x=1449833584; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=keaAS+z2+nwYiNpvOKBh8DQAo5TbvvIX7ujnPH4rt3w=; b=IMgDNDFQMe8R7sWOEEPPpNX+8b9y+Cg9G2z1Z1LXRCyYcKt+sfy5zuMh UwM2JytdyX9zP2BlvY2YXitINwF1za2fim6Ce4GH64917QqkqgOwSdrQv 0TS+aFxM+oY0yswJrdYbWJjig0GAdyuwDqygUkc4Rjino4OmwMWeuG0f6 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ApAgCHPlhW/4wNJK1egztTbwaEJbliA?= =?us-ascii?q?Q2BZBcKhSRKAoE5OBQBAQEBAQEBgQqENAEBAQQBAQE3NAsSAQgRAwECAR43Cx0?= =?us-ascii?q?KBAENBYguDb0tAQEBAQEBAQEBAQEBAQEBAQEBAQEBGItSiTkFh0qFWIk1AYUpi?= =?us-ascii?q?A6BW0mDeYMmjyyDcQEfAQFChARyAYRKgQcBAQE?=
X-IronPort-AV: E=Sophos;i="5.20,351,1444694400"; d="scan'208";a="212439974"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Nov 2015 11:33:03 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id tARBX2e0032345 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 27 Nov 2015 11:33:02 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 27 Nov 2015 05:33:01 -0600
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1104.000; Fri, 27 Nov 2015 05:33:02 -0600
From: "Douglas Gash (dcmgash)" <dcmgash@cisco.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "warren@kumari.net" <warren@kumari.net>
Thread-Topic: OPSAWG Digest, Vol 102, Issue 14 
Thread-Index: AQHRKQdgk2Gksm2h5EuiQ8imlAXB4A==
Date: Fri, 27 Nov 2015 11:33:02 +0000
Message-ID: <D27DE9E1.DCBDA%dcmgash@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.1.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C378B67041115345A28A1A8D17576A84@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/X91GnDNEF9q9UuQj3xj7NCAAGwM>
Cc: "aota@google.com" <aota@google.com>, Thorsten Dahm <thorstendlux@google.com>
Subject: Re: [OPSAWG] OPSAWG Digest, Vol 102, Issue 14
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2015 11:33:06 -0000

Thanks Joe,

You have caught an important typo there, many thanks! In the first upload
of the document (draft-dahm-opsawg-tacacs-00.txt), we used STARTTLS to
upgrade the connection type. Post discussions in Prague, we reverted to
using a separate port for TLS, and documented in the second upload
(draft-dahm-opsawg-tacacs-00.txt). However, I neglected to remove the
packet type for the STARTTLS from the enumeration, so thanks for the
catch. It will be removed on next upload.

Just to confirm, we are proposing separate port rather than STARTTLS.

To your very valid question: in the end, we elected not to add a new
version because we are looking to keep the content of the protocol the
same as the original draft spec (although deprecating some less secure
features). Besides the adoption of a separate port for TLS, this should
help avoid breaking current deployments.

Many Thanks,

Regards,

Thorsten, Andrej, Doug.


>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 16 Nov 2015 14:48:34 -0500
>From: Joe Clarke <jclarke@cisco.com>
>To: Warren Kumari <warren@kumari.net>, "opsawg@ietf.org"
>	<opsawg@ietf.org>
>Subject: Re: [OPSAWG] FW: New Version Notification for
>	draft-dahm-opsawg-tacacs-01.txt
>Message-ID: <564A3312.4030103@cisco.com>
>Content-Type: text/plain; charset=3Dwindows-1252; format=3Dflowed
>
>On 11/13/15 13:37, Warren Kumari wrote:
>> We would really appreciate any feedback on this document. Personally I
>> think it is really useful, but we need the WG to review and provide
>> feedback.
>>
>> Over the years I've heard a number of people kvetch that TACACS+ isn't
>> documented -- well, now you can, you know, actually do something about
>> this...
>
>I may be biased, but I have read the doc, and I support the WG working
>on it.  I agree with your last sentiment that this would be good to
>final document this with industry consensus.
>
>One thing I wonder is if there shouldn't be some version change for the
>support of TLS, or if the Type of 0x00 is enough?
>
>Joe
>
>>
>> W
>>
>> On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
>> <dcmgash@cisco.com> wrote:
>>> Dear Opsawg List,
>>>
>>> We have uploaded a second revision of the TACACS+ protocol
>>>specification
>>> which we believe is ready for publication subject subject to port
>>> allocation.
>>>
>>> Please see details below.
>>>
>>> The essential difference from the first revision is the change of TLS
>>> option support using a separate port as opposed to the original Start
>>>TLS
>>> mechanism.
>>>
>>> We would be very grateful for the opinion of the list regarding the
>>> suitability of document for publication as an RFC.
>>>
>>> Many thanks,
>>>
>>> Thorsten, Andrej, Doug.
>>>
>>>
>>> On 02/10/2015 16:25, "internet-drafts@ietf.org"
>>><internet-drafts@ietf.org>
>>> wrote:
>>>
>>>>
>>>> A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
>>>> has been successfully submitted by Douglas C. Medway Gash and posted
>>>>to
>>>> the
>>>> IETF repository.
>>>>
>>>> Name:          draft-dahm-opsawg-tacacs
>>>> Revision:      01
>>>> Title:         The TACACS+ Protocol
>>>> Document date: 2015-10-02
>>>> Group:         Individual Submission
>>>> Pages:         38
>>>> URL:
>>>> https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
>>>> Status:      =20
>>>>https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
>>>> Htmlized:    =20
>>>>https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
>>>> Diff:
>>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-dahm-opsawg-tacacs-01
>>>>
>>>> Abstract:
>>>>    TACACS+ provides access control for routers, network access servers
>>>>    and other networked computing devices via one or more centralized
>>>>    servers.  TACACS+ provides separate authentication, authorization
>>>>and
>>>>    accounting services.  This document describes the protocol that is
>>>>    used by TACACS+.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>
>>>> The IETF Secretariat
>>>>
>>>
>>
>>
>>
>
>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>OPSAWG mailing list
>OPSAWG@ietf.org
>https://www.ietf.org/mailman/listinfo/opsawg
>
>
>------------------------------
>
>End of OPSAWG Digest, Vol 102, Issue 14
>***************************************


From nobody Fri Nov 27 05:12:08 2015
Return-Path: <dcmgash@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 918651A0194 for <opsawg@ietfa.amsl.com>; Fri, 27 Nov 2015 05:12:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.085
X-Spam-Level: 
X-Spam-Status: No, score=-15.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 eKYU2wdc5dBa for <opsawg@ietfa.amsl.com>; Fri, 27 Nov 2015 05:12:05 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 243E41A0181 for <opsawg@ietf.org>; Fri, 27 Nov 2015 05:12:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5882; q=dns/txt; s=iport; t=1448629925; x=1449839525; h=from:to:cc:subject:date:message-id:mime-version; bh=y3mKWABmRt8tEmPpFqvan3nN0d7bmbysHnICwqvLie8=; b=abNtDAwUur80QtjA9OW2Yod9PpPPosgK+otXrx4/qmr6YDrEZjzzoXr6 g6t/p4VXkMmLgTNNc3FclD2JhwfWBUouB9iwAi/dfrWeNT4G2RJe4i+jH m+hEzI8DpLYVmgTd8vP6eppk8VoDIZzXTjJkmav43eDm8NnBCFnwd3diu Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D3AQC4VVhW/5RdJa1egm5NU28GvhYBD?= =?us-ascii?q?YFkFwEJhSRKAoE0OBQBAQEBAQEBgQqENAEBAQMBAQEBawkCBQ0BCBEDAQIBJy4?= =?us-ascii?q?LFAkKBAENBYgmCA29NgEBAQEBAQEBAQEBAQEBAQEBAQEBFQSLUoR7DQmEKAWHS?= =?us-ascii?q?oYRhRSDaAGNN5xgAR8BAUKEBHKES4EHAQEB?=
X-IronPort-AV: E=Sophos; i="5.20,351,1444694400"; d="scan'208,217"; a="48666888"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Nov 2015 13:12:03 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id tARDC3UK010000 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 27 Nov 2015 13:12:04 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 27 Nov 2015 07:12:03 -0600
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1104.000; Fri, 27 Nov 2015 07:12:03 -0600
From: "Douglas Gash (dcmgash)" <dcmgash@cisco.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>, "owen@delong.com" <owen@delong.com>,  "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Thread-Topic: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs-01.txt
Thread-Index: AQHRKRU1X9EeJgS2N0GffGiF2jQOGw==
Date: Fri, 27 Nov 2015 13:12:03 +0000
Message-ID: <D27DF97E.DCC9E%dcmgash@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.1.4]
Content-Type: multipart/alternative; boundary="_000_D27DF97EDCC9Edcmgashciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/nIYRLF-WEolaIlVqbwFK8g4Qg50>
Cc: "aota@google.com" <aota@google.com>, Thorsten Dahm <thorstendlux@google.com>
Subject: Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2015 13:12:07 -0000

--_000_D27DF97EDCC9Edcmgashciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Eric, Owen,

Thanks for the comments.

The intent at this point is for the "ip" protocol to cover both IPV4 and IP=
V6, as with current practice.

Documenting the format of addresses is an interesting point. Certainly we w=
ould defer detailed representation to the respective RFCs. Up to this point=
, we intended not to reference specific RFCs so that the format is driven b=
y the context, as Owen suggested. We would of course, review that if recomm=
ended by the group.

Many thanks,

Regards,

Doug.

---------- Forwarded message ----------
From: Owen DeLong <owen@delong.com<mailto:owen@delong.com>>
Date: 16 November 2015 at 19:17
Subject: Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs=
-01.txt
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com<mailto:evyncke@cisco.com>>
Cc: "opsawg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsaw=
g@ietf.org>>



> On Nov 16, 2015, at 04:27 , Eric Vyncke (evyncke) <evyncke@cisco.com<mail=
to:evyncke@cisco.com>> wrote:
>
> Important document indeed.
>
> I have a comment on section 7.1 where "ip" as a protocol (the double
> quotes are from the I-D) is mentioned but does it mean IPv4 or IPv6 or
> both?

Surely one would hope that it's meaning is contextual to the time of readin=
g
and that today it would mean {IPv4, IPv6} and that sometime in the future,
it will likely mean {IPv6} and beyond that come to mean {IPv6,...}.

>
> In the same section, may I suggest to describe the syntax of the 'addr'
> field?

Wouldn't the syntax of the addr field be inherently dependent on the
RFC defining the IP version in question in the previous context?

Owen


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>
https://www.ietf.org/mailman/listinfo/opsawg



--
Thorsten Dahm

Network Engineer
Google Ireland Ltd.
The Gasworks, Barrow Street
Dublin 4,  Ireland

Registered in Dublin, Ireland
Registration Number: 368047

--_000_D27DF97EDCC9Edcmgashciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <2DC296BD0D9CB24CA9B9C53B8C907D4B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi Eric, Owen,</div>
<div><br>
</div>
<div>Thanks for the comments.</div>
<div><br>
</div>
<div>The intent at this point is for the &#8220;ip&#8221; protocol to cover=
 both IPV4 and IPV6, as with current practice.</div>
<div><br>
</div>
<div>Documenting the format of addresses is an interesting point. Certainly=
 we would defer detailed representation to the respective RFCs. Up to this =
point, we intended not to reference specific RFCs so that the format is dri=
ven by the context, as Owen suggested.
 We would of course, review that if recommended by the group.</div>
<div><br>
</div>
<div>Many thanks,</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Doug.&nbsp;</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_quote">---------- Forwarded message ----------<br>
From: <b class=3D"gmail_sendername">Owen DeLong</b> <span dir=3D"ltr">&lt;<=
a href=3D"mailto:owen@delong.com">owen@delong.com</a>&gt;</span><br>
Date: 16 November 2015 at 19:17<br>
Subject: Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs=
-01.txt<br>
To: &quot;Eric Vyncke (evyncke)&quot; &lt;<a href=3D"mailto:evyncke@cisco.c=
om">evyncke@cisco.com</a>&gt;<br>
Cc: &quot;<a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a>&quot; &lt;=
<a href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a>&gt;<br>
<br>
<br>
<span class=3D""><br>
&gt; On Nov 16, 2015, at 04:27 , Eric Vyncke (evyncke) &lt;<a href=3D"mailt=
o:evyncke@cisco.com">evyncke@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Important document indeed.<br>
&gt;<br>
&gt; I have a comment on section 7.1 where &quot;ip&quot; as a protocol (th=
e double<br>
&gt; quotes are from the I-D) is mentioned but does it mean IPv4 or IPv6 or=
<br>
&gt; both?<br>
<br>
</span>Surely one would hope that it&#8217;s meaning is contextual to the t=
ime of reading<br>
and that today it would mean {IPv4, IPv6} and that sometime in the future,<=
br>
it will likely mean {IPv6} and beyond that come to mean {IPv6,&#8230;}.<br>
<span class=3D""><br>
&gt;<br>
&gt; In the same section, may I suggest to describe the syntax of the 'addr=
'<br>
&gt; field?<br>
<br>
</span>Wouldn&#8217;t the syntax of the addr field be inherently dependent =
on the<br>
RFC defining the IP version in question in the previous context?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Owen<br>
</font></span>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
_______________________________________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/opsawg</a><br>
</div>
</div>
</div>
<br>
<br clear=3D"all">
<div><br>
</div>
-- <br>
<div class=3D"gmail_signature">Thorsten Dahm<br>
<br>
Network Engineer<br>
Google Ireland Ltd.<br>
The Gasworks, Barrow Street<br>
Dublin 4,&nbsp; Ireland<br>
<br>
Registered in Dublin, Ireland<br>
Registration Number: 368047</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D27DF97EDCC9Edcmgashciscocom_--


From nobody Mon Nov 30 16:15:02 2015
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E30B81B33B1 for <opsawg@ietfa.amsl.com>; Mon, 30 Nov 2015 16:15:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
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 PAKUO7m6pu7B for <opsawg@ietfa.amsl.com>; Mon, 30 Nov 2015 16:14:59 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (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 F170D1B2AF2 for <opsawg@ietf.org>; Mon, 30 Nov 2015 16:14:58 -0800 (PST)
Received: by ykdr82 with SMTP id r82so204978015ykd.3 for <opsawg@ietf.org>; Mon, 30 Nov 2015 16:14:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=IVgznUAN4dKW1K4utAu7lAyHiEF2oelqwEtycGC+OC4=; b=tRm8MTHNrVMLwiQrHd7XMteT2khz1LCvlSrKQHk3ELC5CCOUKybfJUCUwVwxirEqnX fRpqiwO5pRPvSr+HyvnEf7e0RDpmxWnwne7H35NxkmMHpbxVQP+W15sB/NBcGkhpTc/J wS/tTGwxxOempxpXCkVwGZ08QXrfMtCk6BkzYWGWhAhpwmVO+JCpglvaZXe4kH7bhh5g hOAZJWp/uSzO/l1Fm27xgt57veT1LyZoIwQpcCRhzaA/jKOnfiUt0i4k07mc16U5LWoS x4Oa27VmHq1szNAU6hIwCqVJbgacuCB/+vjNM2SyOLuSBctWHJ5ldTY662XDkeBl7kNu YEAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=IVgznUAN4dKW1K4utAu7lAyHiEF2oelqwEtycGC+OC4=; b=PsPRkLaCtAuWcQ9uh6l4qAyrI8koo4a5hbTbiJ+XC+FfQfvyF8xTabi2i41y4arQMJ YCg0o0IgxVGCcCMaeocHg7jl23rBlc5Q+SSSPyUNyNBS6plN8uTXGWruR487LFPDUJ/f PEFkyga3mSPU/LR3NqFJdZw1vxNt0JXQjXHt7cKfDfDGs1KD/yziL3aFWJWEDpD3iqAs 2Ez4z3anmkMVgLaxUTnQDf9sgPjwYNUlCRbgfoHSO/L9kKQprVQ9duUVdn7A+KmzHWGL WHtrG8QsySj8hj5J2Y1OJSFvyz3wBELGgQR/Xl4hGiyoGZdwL06RKvuO7FqoFHA/Kq5M sFAg==
X-Gm-Message-State: ALoCoQkPLNgOMt4FMOCWAKl2MLYDSZRuN/UoBjBSG0VRor2S+5FEJOJodLN/6r9gEZU0DpDM7xYa
X-Received: by 10.129.93.133 with SMTP id r127mr54962501ywb.109.1448928898116;  Mon, 30 Nov 2015 16:14:58 -0800 (PST)
MIME-Version: 1.0
References: <20151002152505.26594.74925.idtracker@ietfa.amsl.com> <D237455F.BC00F%dcmgash@cisco.com> <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
In-Reply-To: <CAHw9_iKOM5N3-HS3ZOFFaDHYTV7rDaf3YHo-dEmdTU9-4W49aw@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 01 Dec 2015 00:14:48 +0000
Message-ID: <CAHw9_iKebHhnE0wSrAVGyz8sVHX7gMoPFy+rkr5SoWyAqEfxFQ@mail.gmail.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: multipart/alternative; boundary=001a114d8bc64720290525cb0ced
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/1hB3Nkw1KcsSvrNlOcelGV2dJfM>
Subject: Re: [OPSAWG] FW: New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2015 00:15:01 -0000

--001a114d8bc64720290525cb0ced
Content-Type: text/plain; charset=UTF-8

Dear OpsAWG,

The chairs believe that there is sufficient interest and support to adopt
this document as an OpsAWG document.

Authors, please resubmit as draft-ietf-opsawg-tacacs-01

Working group:
We would like to see this document progress, and are hoping to WGLC it
soon. Please review this and provide feedback....

W

On Fri, Nov 13, 2015 at 1:37 PM Warren Kumari <warren@kumari.net> wrote:

> We would really appreciate any feedback on this document. Personally I
> think it is really useful, but we need the WG to review and provide
> feedback.
>
> Over the years I've heard a number of people kvetch that TACACS+ isn't
> documented -- well, now you can, you know, actually do something about
> this...
>
> W
>
> On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)
> <dcmgash@cisco.com> wrote:
> > Dear Opsawg List,
> >
> > We have uploaded a second revision of the TACACS+ protocol specification
> > which we believe is ready for publication subject subject to port
> > allocation.
> >
> > Please see details below.
> >
> > The essential difference from the first revision is the change of TLS
> > option support using a separate port as opposed to the original Start TLS
> > mechanism.
> >
> > We would be very grateful for the opinion of the list regarding the
> > suitability of document for publication as an RFC.
> >
> > Many thanks,
> >
> > Thorsten, Andrej, Doug.
> >
> >
> > On 02/10/2015 16:25, "internet-drafts@ietf.org" <
> internet-drafts@ietf.org>
> > wrote:
> >
> >>
> >>A new version of I-D, draft-dahm-opsawg-tacacs-01.txt
> >>has been successfully submitted by Douglas C. Medway Gash and posted to
> >>the
> >>IETF repository.
> >>
> >>Name:          draft-dahm-opsawg-tacacs
> >>Revision:      01
> >>Title:         The TACACS+ Protocol
> >>Document date: 2015-10-02
> >>Group:         Individual Submission
> >>Pages:         38
> >>URL:
> >>https://www.ietf.org/internet-drafts/draft-dahm-opsawg-tacacs-01.txt
> >>Status:
> https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/
> >>Htmlized:       https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01
> >>Diff:
> >>https://www.ietf.org/rfcdiff?url2=draft-dahm-opsawg-tacacs-01
> >>
> >>Abstract:
> >>   TACACS+ provides access control for routers, network access servers
> >>   and other networked computing devices via one or more centralized
> >>   servers.  TACACS+ provides separate authentication, authorization and
> >>   accounting services.  This document describes the protocol that is
> >>   used by TACACS+.
> >>
> >>
> >>
> >>
> >>
> >>Please note that it may take a couple of minutes from the time of
> >>submission
> >>until the htmlized version and diff are available at tools.ietf.org.
> >>
> >>The IETF Secretariat
> >>
> >
>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>    ---maf
>

--001a114d8bc64720290525cb0ced
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear OpsAWG,<div><br></div><div>The chairs believe that th=
ere is sufficient interest and support to adopt this document as an OpsAWG =
document.</div><div><br></div><div>Authors, please resubmit as=C2=A0draft-i=
etf-opsawg-tacacs-01<br><br>Working group:=C2=A0</div><div>We would like to=
 see this document progress, and are hoping to WGLC it soon. Please review =
this and provide feedback....</div><div><br></div><div>W<br><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Fri, Nov 13, 2015 at 1:37 PM Warren Ku=
mari &lt;<a href=3D"mailto:warren@kumari.net">warren@kumari.net</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">We would really appreciate any =
feedback on this document. Personally I<br>
think it is really useful, but we need the WG to review and provide<br>
feedback.<br>
<br>
Over the years I&#39;ve heard a number of people kvetch that TACACS+ isn&#3=
9;t<br>
documented -- well, now you can, you know, actually do something about<br>
this...<br>
<br>
W<br>
<br>
On Sun, Oct 4, 2015 at 4:18 PM, Douglas Gash (dcmgash)<br>
&lt;<a href=3D"mailto:dcmgash@cisco.com" target=3D"_blank">dcmgash@cisco.co=
m</a>&gt; wrote:<br>
&gt; Dear Opsawg List,<br>
&gt;<br>
&gt; We have uploaded a second revision of the TACACS+ protocol specificati=
on<br>
&gt; which we believe is ready for publication subject subject to port<br>
&gt; allocation.<br>
&gt;<br>
&gt; Please see details below.<br>
&gt;<br>
&gt; The essential difference from the first revision is the change of TLS<=
br>
&gt; option support using a separate port as opposed to the original Start =
TLS<br>
&gt; mechanism.<br>
&gt;<br>
&gt; We would be very grateful for the opinion of the list regarding the<br=
>
&gt; suitability of document for publication as an RFC.<br>
&gt;<br>
&gt; Many thanks,<br>
&gt;<br>
&gt; Thorsten, Andrej, Doug.<br>
&gt;<br>
&gt;<br>
&gt; On 02/10/2015 16:25, &quot;<a href=3D"mailto:internet-drafts@ietf.org"=
 target=3D"_blank">internet-drafts@ietf.org</a>&quot; &lt;<a href=3D"mailto=
:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&g=
t;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;A new version of I-D, draft-dahm-opsawg-tacacs-01.txt<br>
&gt;&gt;has been successfully submitted by Douglas C. Medway Gash and poste=
d to<br>
&gt;&gt;the<br>
&gt;&gt;IETF repository.<br>
&gt;&gt;<br>
&gt;&gt;Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 draft-dahm-opsawg-tacacs<br=
>
&gt;&gt;Revision:=C2=A0 =C2=A0 =C2=A0 01<br>
&gt;&gt;Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The TACACS+ Protocol<br>
&gt;&gt;Document date: 2015-10-02<br>
&gt;&gt;Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Individual Submission<br>
&gt;&gt;Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A038<br>
&gt;&gt;URL:<br>
&gt;&gt;<a href=3D"https://www.ietf.org/internet-drafts/draft-dahm-opsawg-t=
acacs-01.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/int=
ernet-drafts/draft-dahm-opsawg-tacacs-01.txt</a><br>
&gt;&gt;Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatra=
cker.ietf.org/doc/draft-dahm-opsawg-tacacs/" rel=3D"noreferrer" target=3D"_=
blank">https://datatracker.ietf.org/doc/draft-dahm-opsawg-tacacs/</a><br>
&gt;&gt;Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.o=
rg/html/draft-dahm-opsawg-tacacs-01" rel=3D"noreferrer" target=3D"_blank">h=
ttps://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01</a><br>
&gt;&gt;Diff:<br>
&gt;&gt;<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-dahm-opsawg-ta=
cacs-01" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
url2=3Ddraft-dahm-opsawg-tacacs-01</a><br>
&gt;&gt;<br>
&gt;&gt;Abstract:<br>
&gt;&gt;=C2=A0 =C2=A0TACACS+ provides access control for routers, network a=
ccess servers<br>
&gt;&gt;=C2=A0 =C2=A0and other networked computing devices via one or more =
centralized<br>
&gt;&gt;=C2=A0 =C2=A0servers.=C2=A0 TACACS+ provides separate authenticatio=
n, authorization and<br>
&gt;&gt;=C2=A0 =C2=A0accounting services.=C2=A0 This document describes the=
 protocol that is<br>
&gt;&gt;=C2=A0 =C2=A0used by TACACS+.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;Please note that it may take a couple of minutes from the time of<b=
r>
&gt;&gt;submission<br>
&gt;&gt;until the htmlized version and diff are available at <a href=3D"htt=
p://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>=
.<br>
&gt;&gt;<br>
&gt;&gt;The IETF Secretariat<br>
&gt;&gt;<br>
&gt;<br>
<br>
<br>
<br>
--<br>
I don&#39;t think the execution is relevant when it was obviously a bad<br>
idea in the first place.<br>
This is like putting rabid weasels in your pants, and later expressing<br>
regret at having chosen those particular rabid weasels and that pair<br>
of pants.<br>
=C2=A0 =C2=A0---maf<br>
</blockquote></div></div></div>

--001a114d8bc64720290525cb0ced--


From nobody Mon Nov 30 19:32:22 2015
Return-Path: <rdrake@direcpath.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B0B1B38C5 for <opsawg@ietfa.amsl.com>; Mon, 30 Nov 2015 19:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001] autolearn=ham
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 5Aaa_cQoRpTS for <opsawg@ietfa.amsl.com>; Mon, 30 Nov 2015 19:32:18 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0673.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:673]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2C1C1B38C4 for <opsawg@ietf.org>; Mon, 30 Nov 2015 19:32:17 -0800 (PST)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=rdrake@direcpath.com; 
Received: from [10.6.2.149] (24.98.60.52) by BY2PR01MB1719.prod.exchangelabs.com (10.163.26.145) with Microsoft SMTP Server (TLS) id 15.1.331.20; Tue, 1 Dec 2015 03:31:55 +0000
From: Robert Drake <rdrake@direcpath.com>
To: <opsawg@ietf.org>
References: <D27DF97E.DCC9E%dcmgash@cisco.com>
Message-ID: <565D14A5.7040204@direcpath.com>
Date: Mon, 30 Nov 2015 22:31:49 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Thunderbird/42.0
MIME-Version: 1.0
In-Reply-To: <D27DF97E.DCC9E%dcmgash@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [24.98.60.52]
X-ClientProxiedBy: CY1PR01CA0026.prod.exchangelabs.com (25.163.94.36) To BY2PR01MB1719.prod.exchangelabs.com (25.163.26.145)
X-Microsoft-Exchange-Diagnostics: 1; BY2PR01MB1719; 2:Oz67IRSwVYNLVGPX/g1Oa088aLHVNr0wW+uG+C/MpHsnxX50FSwSlv5uXxEuaO24fcKU1DTQsE1yiRiUUJnust0RY0QqZto2kLyu4JFlLYVze8JkVZXJOd9B5ra3y2YE+6e16smqpE3meDESzF+rYw==; 3:AA2QXzTBQ4qCtd3DigkzyWpyzscXvXCP205nl04O6L4cfdKI2UubSbKAGk5AeW0izEYCcEq1qrXnmru6KWuvrZiofJDubZUz6DazIOf/vGa+Cm62fFCTp5VKjXR2H/AB; 25:EQ71kaThyODXsvkvQjPrbgTC7vLJISuH9WTEdyCeQQSzrVVhJHpw3hgsmnkCEeyWIv6whwBEwgW7Nl5xuilin2Ob7yrCcRGDtDvJ7fOw1jorpRI8JV6q3sAlsJ4cZBhernEZeF18VS7x7qlv6LLEuUGyPcqWzkFxxScua20waKhHrQ/eyrly83QbTG9qV2xhVV8gCOs2NC5EVkbiJb+guhqGunPLW4apqqcI6P6nbuoOAMSSBO29ptJMLSUGNMyE; 4:VI8g+NZlOYOSdClUOZLpFwIoQf4ky97CGEURqVUU0S3K9JkvgFCqDtuErAPYTEioPypZ0/1wNB3whJ2JCPRIgexqlqElM7jOAchNFFy33tiDYQ7kk2VValGhYhJDZ0TngfierqYpZ15YYzt6NROVdVI79s3ey4jqp5u1OvW/y20DoemWnZvZYFXINo6zxegv3d9EoWm8+xHwRPazL05lqTlKzIJTVCwwV3RIS2ycMzB0hli7xhdJD+GTKOqTGdJHRLAJPwmlx/DVN36Bemigi/lP3vDiSTnQZtdAfNpjedUa/OXmbs+GGeTCMBaBZVBX0Z6fTkNDi6lOBvP48nIckIj0xU4bkigi/oJQwiLz9sqLFvrlh97fSuXsQsq6usAx
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR01MB1719;
X-Microsoft-Antispam-PRVS: <BY2PR01MB171911E72DBBAE4A18AD63B6CA0F0@BY2PR01MB1719.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(8121501046)(520078)(3002001)(10201501046); SRVR:BY2PR01MB1719; BCL:0; PCL:0; RULEID:; SRVR:BY2PR01MB1719; 
X-Forefront-PRVS: 07778E4001
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(189002)(199003)(230783001)(5004730100002)(19580405001)(586003)(77096005)(2351001)(2950100001)(50466002)(66066001)(122386002)(86362001)(40100003)(230700001)(450100001)(65956001)(65806001)(83506001)(42186005)(47776003)(19580395003)(106356001)(33656002)(64126003)(105586002)(50986999)(65816999)(87976001)(5001960100002)(97736004)(87266999)(3846002)(6116002)(81156007)(76176999)(36756003)(80316001)(92566002)(23746002)(1096002)(5008740100001)(4001350100001)(110136002)(107886002)(54356999)(101416001)(59896002)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR01MB1719; H:[10.6.2.149]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: direcpath.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; BY2PR01MB1719; 23:iXRKqBlccN4gt74qXNbLpG0iqplvBqlorZTMn?= =?Windows-1252?Q?Cd3f/UF2dosbmpqa8ZVHgDi8GYpkTEYGOOe7qWQTioraQz6y81NeZJQA?= =?Windows-1252?Q?Dnd1NUf5iDqR6Y8zgURayZF/cnnIrfSfF73EQ+iFxvCpUeNp39lv8q8d?= =?Windows-1252?Q?Ap3+pv0VT4L+/7pvNZZYHxRJSsiUZRM+CipxDiLyiD5DIPKhubgIkYJE?= =?Windows-1252?Q?DuJBG1WZ7/UJ0UMLri4v1GS+zkKA4UljFvi0tGgbUzyMDv4XpkgppIZo?= =?Windows-1252?Q?RQ0PSO2UW13q3rCKtjh0e5s1DSeJvWPlRZDcfvAQtBV1VZ8BNoWdsNTF?= =?Windows-1252?Q?FO73IiZkpD6l6Z+ac7oKMv/7xstMn86729PKRNU4OHeYmQ7XTXRvW5+J?= =?Windows-1252?Q?pFs7GK+udRrLZueEs6Ot1jEOzA9nAyeuBc2K+de3pQlONXm/afmtqxFt?= =?Windows-1252?Q?ID8LSoCyqV2DqnjvQjj8uJVK5OtwbIxbplU+UFdKYFGxRKaluFgErbUi?= =?Windows-1252?Q?Bs4ewoOuvCv1Whq4wzU4fYyVRmqAnIIurbtQdmZPJ/XC0Xkrc0XJgRTw?= =?Windows-1252?Q?YaAomOiqvMqtBOYwcVaGeI7zM/U0F4Y45GbC/Yi9nxyNmH2IXMRg0y27?= =?Windows-1252?Q?ihs1dZ8y8vm5rDMI7iEkm552UO0Y83rf+UNuYGZYsxOi35+4ccw685no?= =?Windows-1252?Q?WmBYwVc1x41PdcCor/8VYRwX4QhhmScDZTNQfzWtsAZmOcLLORWBe3DW?= =?Windows-1252?Q?+vJneiPqoW3mHP4ul/7fX6qQPFu7yPPjvwTleoAMKKL/3WqMfZaSYQwd?= =?Windows-1252?Q?UPV+jRCSZriuWjFY/evScxH6BPB+wu5OFZrHZDam143XeZDR30XE1JRj?= =?Windows-1252?Q?rkRihdSRsxluh2YeoYEQk3JOeFMjzJHnuSPEVlKcRKKZcJaPrURs80P6?= =?Windows-1252?Q?cuYdIJv4a9rIOlzuSwlym4uL6y3I6kmqzRZQfDUJqRDPMA0akf9cGi+1?= =?Windows-1252?Q?fwArTX/ZHEIrYTjyjmInVUuMwJi+bY6CqhNlcYQhNnAsLab5v/+beO7b?= =?Windows-1252?Q?jp1H33ooD6SunyetrqfxZCkNnEVr95FfDsXnTjfjWVgUKGepTWC9ED0G?= =?Windows-1252?Q?9tqlLlPDLwf2uSM2KwS4JeZKNx5o8n292foRG0aZr8gedIliyuQmaAho?= =?Windows-1252?Q?kNd5/ZVgT5vg6dh10S9XeqmM7BwoIvibQC/hpw6XkHtibQRQf16W3WgS?= =?Windows-1252?Q?mASmQKBdTFlM4rlSERUeDRdS9Aihr7aOxHlXEwJTjEWXy3zLvvOUS7SB?= =?Windows-1252?Q?d45IJz9w+hF1XCNT1avrKFv3lNKgIrSaa0R6gFrKUEimHWt6zt0tFhEL?= =?Windows-1252?Q?pmfTHW6wV5oY/fG1xb9RnekoYhQsi7DXg=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR01MB1719; 5:0YDf4N51O6rYxhh2AW4nM+pHq2Ei2C4Ccdje5i4s/ZYjT68hr0dRgn1HU/JNjYwKiPJqLHD3Q8v0rZ2YGMFzjgo0FqKYeORTU8Nr56i/B9aonr0kwgw8VIGH5kJPci7cCfG9j48X9KvXUCIIStdERw==; 24:wKMJ6RhlCS9EMfsIQ03DRJ8OVxvxLKS7ukp/1XmxSToe82fw0V1R2B8ODhmnuZYufBd8AEksjwx6F2QYLeiTufW51euyLjMBMjII6nzrqgs=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: direcpath.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Dec 2015 03:31:55.1131 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR01MB1719
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/wkPFrCGtaOdlfM_k05L0MiWKNQw>
Subject: Re: [OPSAWG] New Version Notification for draft-dahm-opsawg-tacacs-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2015 03:32:21 -0000

I read through the draft and found a couple of minor items that might 
help with readability.  Please excuse me if this has been covered 
already.  I searched the archives but didn't find these specific things.

1.  Introduction/Status of this Memo

The introduction repeats much of the text from Status of this Memo. It 
also includes text saying the document expires on December 10, 2015 (the 
old expiration date from -00).  You can probably remove all of that.

2.  ''The Draft'' is mentioned before being defined

Technically it's never really defined, but [TheDraft] is a reference and 
I know what was intended.  It would be nice if it was treated as a link 
by the HTMLifier like the RFC/BCP statements.  It might be converted if 
the reference is put beside each use, I'm not familiar with the way the 
HTML thing works.

It might also be nice just to include a blurb before the first mention, 
or rewrite the paragraph to define it.

"A wide range of TACACS+ clients and servers are already deployed in the 
field, based upon a draft RFC from 1997 [TheDraft], hereafter referred 
to as ''The Draft''."

Finally, I want to say that I really appreciate you guys working on 
this.  TACACS+ has security and convenience issues that I've lived with 
all my network life.  I would very much like to see this adopted.

Also, I'm not sure if this is a fault of it being a draft or if it's 
easy to fix, but the email address listed in 
tools.ietf.org/html/draft-dahm-opsawg-tacacs-01 
(draft-dahm-opsawg-tacacs@tools.ietf.org) bounces.

