(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*

This guide provides a more detailed description of the syntax that is supported along with examples.

This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.

Concept Search - What can I type?

For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.

Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.

Accounting Requirements for IPng (RFC1672)

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Brownlee: AUTHOR

Abstract

This document was submitted to the IETF IPng area in response to RFC 1550. Publication of this document does not imply acceptance by the IPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.

Country

United States

Language

English (United States)

This text was extracted from an ASCII text file.

This is the abbreviated version, containing approximately
45% of the total text.

Network Working Group N.
Brownlee
Request for Comments: 1672
The University of Auckland
Category: Informational August
1994

Accounting
Requirements for IPng

Status of this Memo

This memo
provides information for the Internet community. This memo
does not specify an Internet standard
of any kind. Distribution of
this memo is unlimited.

Abstract

This document
was submitted to the IETF IPng area in response to RFC
1550.
Publication of this document does not imply acceptance by the
IPng area of any ideas expressed
within. Comments should be
submitted to the
big-internet@munnari.oz.au mailing list.

Summary

This white paper
discusses accounting requirements for IPng. It
recommends that all IPng packets carry
accounting tags, which would
vary in size. In the simplest case a
tag would simply be a voucher
identifying the party responsible for
the packet. At other times tags
should also carry other higher-level
accounting information.

Background

The Internet
Accounting Model - described in RFC 1272 - specifies how
accounting information is structured,
and how it is collected for use
by accounting aplications. The model is very general, with
accounting variables being defined for
various layers of a protocol
stack.
The group's work has so far concentrated on the lower layers,
but the model can be extended simply
by defining the variables
required, e.g., for session and
application layers.

Brian Carpenter
[1] suggests that IPng packets should carry
authenticated (source, destination,
transaction) triplets, which
could be used for policy-based routing
and accounting. The following
sections explain how the transaction
field - hereafter called an
'accounting tag' - could be used.

Lower-layer (Transport) Accounting

At the lower
(network) layers the tag would simply be a voucher. This
means it is an arbitrary string which
identifies the party

responsible, i.e., willing to pay for,
a packet. It would initially
be set by the host which originates
the packet, hence at that stage
the tag would identify the user who
sent it.

A tag could be
changed at various points along a packet's path. This
could be done as part of the routing
policy processing so as to
reflect changes of the party responsible over each section of the
path. For example: