CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 04:06:44 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=.ynUPPJhxkR3xfJ5KUdMmIRrr0eYgfJrsyBb5kNiQIk-1760069204-1.0.1.1-NN8OHSAerMXPWcKHcqoQMipctgSWkLt5XHCPApm6_BN7D7aoQZIolBRJK1u7zHtAp6VlrhLMn4qOXtfw_KNTHTAh14FkIRuHRvBHjXQK_GY; path=/; expires=Fri, 10-Oct-25 04:36:44 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c33f27bed8a8b0-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 7856 » RFC Editor
Search RFCs
RFC 7856
Softwire Mesh Management Information Base (MIB), May 2016
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- Y. Cui
J. Dong
P. Wu
M. Xu
A. Yla-Jaaski - Stream:
- IETF
- Source:
- softwire (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7856
Discuss this RFC: Send questions or comments to the mailing list softwires@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7856
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing a softwire mesh.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us