[OPSAWG] TACACS+ Information Document Diffs Version 6-10

[Douglas Gash (dcmgash)]

Dear OPSAWG,

Please find below a first attempt to run through the differences between the 
document version 6 (Feb 10 2017) and version 10 (April 15 2018).

The Diff was generated using the “Change Bar” option of the Document History 
page. (https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/history/)

Each highlighted difference has a short, capitalized description. The security 
section is removed as this is being handled in a different thread.

Please let us know:

-if clarifications are required for the changed. They are pretty terse.
-if the changes need adjustments.

There will be another upload shortly, at least for the security section. When 
we do the next upload we’ll provide a similar treatment.

If this treatment itself is insufficient, please let us know.

Many thanks.
 
 Operations   T. Dahm
 Internet-DraftA. Ota
 Intended status: InformationalGoogle Inc
|Expires: October 17, 2018 D. Medway Gash
AUTO ADMIN CHANGE
  Cisco Systems, Inc.
D. Carrel
vIPtela, Inc.
 L. Grant
|  April 15, 2018
AUTO ADMIN CHANGE
 
   The TACACS+ Protocol
|  draft-ietf-opsawg-tacacs-10
AUTO ADMIN CHANGE
 
 Abstract
 
TACACS+ provides Device Administration for routers, network access
servers and other networked computing devices via one or more
centralized servers.  This document describes the protocol that is
used by TACACS+.
 
 Status of This Memo
 
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
 
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF).  Note that other groups may also distribute
working documents as Internet-Drafts.  The list of current Internet-
|   Drafts is at https://datatracker.ietf.org/drafts/current/.
AUTO ADMIN CHANGE
 
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
 
|   This Internet-Draft will expire on October 17, 2018.
AUTO ADMIN CHANGE
 
 Copyright Notice
 
|   Copyright (c) 2018 IETF Trust and the persons identified as the
AUTO ADMIN CHANGE
document authors.  All rights reserved.
 
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
|   (https://trustee.ietf.org/license-info) in effect on the date of
AUTO ADMIN CHANGE
publication of this document.  Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.  Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
 
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008.  The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
 
 Table of Contents
 
1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
2.  Technical Definitions . . . . . . . . . . . . . . . . . . . .   4
3.  TACACS+ Connections and Sessions  . . . . . . . . . . . . . .   4
  3.1.  Connection  . . . . . . . . . . . . . . . . . . . . . . .   4
| 3.2.  Session . . . . . . . . . . . . . . . . . . . . . . . . .   5
| 3.3.  Single Connection Mode  . . . . . . . . . . . . . . . . .   5
| 3.4.  Session Completion  . . . . . . . . . . . . . . . . . . .   6
| 3.5.  Treatment of Enumerated Protocol Values . . . . . . . . .   7
  3.6.  Text Encoding . . . . . . . . . . . . . . . . . . . . . .   7
  3.7.  Data Obfuscation  . . . . . . . . . . . . . . . . . . . .   7
  3.8.  The TACACS+ Packet Header . . . . . . . . . . . . . . . .   9
  3.9.  The TACACS+ Packet Body . . . . .

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-ipfix-bgp-community-07.txt

[li zhenqiang]

Hello all,

The new version is updated according to the review results from gen-art and 
routing directorate, the follow-up discussion of the review result, and 
valueable comments from Paul Aitken. Thank you all very much.

Since that, more than three weeks, no more comments are raised. So, the WG 
please consider to move it forward. Thanks

Best Regards,
Zhenqiang Li

li_zhenqi...@hotmail.com

From: internet-drafts
Date: 2018-05-12 22:24
To: i-d-annou...@ietf.org
CC: opsawg
Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-ipfix-bgp-community-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group 
WG of the IETF.

Title   : Export BGP community information in IP Flow 
Information Export (IPFIX)
Authors : Zhenqiang Li
  Rong Gu
  Jie Dong
Filename: draft-ietf-opsawg-ipfix-bgp-community-07.txt
Pages   : 20
Date: 2018-05-12

Abstract:
   By introducing new Information Elements (IEs), this draft extends the
   existing BGP related IEs to enable IPFIX [RFC7011] to export the BGP
   community information, including the information of BGP standard
   community [RFC1997], BGP extended community [RFC4360], and BGP large
   community [RFC8092].  Network traffic information can then be
   accumulated and analysed at the BGP community granularity, which
   represents the traffic of different kinds of customers, services, or
   geographical regions according to the network operator's BGP
   community planning.  Network traffic information at the BGP community
   granularity is useful for network traffic analysis and engineering.

   To clarify, no new BGP community attribute is defined in this
   document and this document has no purpose to replace BGP Monitoring
   Protocol (BMP) defined in RFC7854.  The IEs introduced in this
   document are used by IPFIX together with other IEs to facilitate the
   IPFIX collector analyzing the network traffic at the BGP community
   granularity without running the heavy BGP protocol.  When needed, the
   mediator or collector can use the IEs introduced in this document to
   report the BGP community related traffic flow information it gets
   either from exporters or through local correlation to other IPFIX
   devices.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-bgp-community/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-opsawg-ipfix-bgp-community-07
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-bgp-community-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-ipfix-bgp-community-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] I-D Action: draft-ietf-opsawg-ipfix-bgp-community-07.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group 
WG of the IETF.

Title   : Export BGP community information in IP Flow 
Information Export (IPFIX)
Authors : Zhenqiang Li
  Rong Gu
  Jie Dong
Filename: draft-ietf-opsawg-ipfix-bgp-community-07.txt
Pages   : 20
Date: 2018-05-12

Abstract:
   By introducing new Information Elements (IEs), this draft extends the
   existing BGP related IEs to enable IPFIX [RFC7011] to export the BGP
   community information, including the information of BGP standard
   community [RFC1997], BGP extended community [RFC4360], and BGP large
   community [RFC8092].  Network traffic information can then be
   accumulated and analysed at the BGP community granularity, which
   represents the traffic of different kinds of customers, services, or
   geographical regions according to the network operator's BGP
   community planning.  Network traffic information at the BGP community
   granularity is useful for network traffic analysis and engineering.

   To clarify, no new BGP community attribute is defined in this
   document and this document has no purpose to replace BGP Monitoring
   Protocol (BMP) defined in RFC7854.  The IEs introduced in this
   document are used by IPFIX together with other IEs to facilitate the
   IPFIX collector analyzing the network traffic at the BGP community
   granularity without running the heavy BGP protocol.  When needed, the
   mediator or collector can use the IEs introduced in this document to
   report the BGP community related traffic flow information it gets
   either from exporters or through local correlation to other IPFIX
   devices.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-bgp-community/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-opsawg-ipfix-bgp-community-07
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-bgp-community-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-ipfix-bgp-community-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg