dido:public:ra:xapend:xapend.b_stds:tech:ietf:6891
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:ietf:6891 [2020/11/13 02:28] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:tech:ietf:6891 [2021/08/18 11:29] (current) murphy [Introduction] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== RFC6891 - Extension Mechanisms for DNS (EDNS(0)) ===== | ===== RFC6891 - Extension Mechanisms for DNS (EDNS(0)) ===== | ||
| - | [[dido:public:ra:xapend:xapend.b_stds:tech:ietf| return to the IETF Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]] |
| <table> | <table> | ||
| Line 15: | Line 15: | ||
| ==== Introduction ==== | ==== Introduction ==== | ||
| - | : //The Domain Name System's wire protocol includes a number of fixed | + | : //The [[dido:public:ra:xapend:xapend.a_glossary:d:dns|Domain Name System's]] [[dido:public:ra:xapend:xapend.a_glossary:w:wireprotocol|wire protocol]] includes a number of fixed |
| fields whose range has been or soon will be exhausted and does not | fields whose range has been or soon will be exhausted and does not | ||
| allow requestors to advertise their capabilities to responders. This | allow requestors to advertise their capabilities to responders. This | ||
| document describes backward-compatible mechanisms for allowing the | document describes backward-compatible mechanisms for allowing the | ||
| - | protocol to grow.// | + | [[dido:public:ra:xapend:xapend.a_glossary:p:protocol|protocol]] to grow.// |
| - | : //This document updates the Extension Mechanisms for [[dido:public:ra:xapend:xapend.glossary:d:dns]] (EDNS(0)) | + | : //This document updates the Extension Mechanisms for [[dido:public:ra:xapend:xapend.a_glossary:d:dns]] (EDNS(0)) |
| specification (and obsoletes RFC 2671) based on feedback from | specification (and obsoletes RFC 2671) based on feedback from | ||
| deployment experience in several implementations. It also obsoletes | deployment experience in several implementations. It also obsoletes | ||
| RFC 2673 ("Binary Labels in the Domain Name System") and adds | RFC 2673 ("Binary Labels in the Domain Name System") and adds | ||
| considerations on the use of extended labels in the DNS.// | considerations on the use of extended labels in the DNS.// | ||
| + | |||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/tech/ietf/6891.1605252536.txt.gz · Last modified: 2020/11/13 02:28 by nick
