> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/ja/ptaru/akusesutorru/rules/katarogu.md).

# 属性カタログ

<figure><img src="https://992520889-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWU1DQ4UGkqER7uGNUOm%2Fuploads%2F2zuSMUw6nxABZMD0FRCK%2Fimage.png?alt=media&amp;token=85f01acd-1b32-41c7-85e6-8994b47e43cb" alt=""><figcaption></figcaption></figure>

属性カタログは、ルールで返すことを許可された RADIUS 属性の選択リストです。標準の VLAN/トンネル属性（DHCP-IEEE-802.1Q-VLAN-ID、SN-Assigned-VLAN-ID、Egress-VLANID、およびベンダー固有の同等項目）に加え、Filter-Id、Class、Framed-MTU、Tunnel-Password などの他の RADIUS 属性や、Cisco-AVPair、Fortinet-Group-Name のようなベンダー固有のものも含まれます。ここで属性を追加すると、そのルールの割り当てで選択可能になるだけで、単独でどこかに適用されることはありません。まだ一覧にない属性は、RADIUS ディクショナリを検索することで追加できます。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.radiusaas.com/ja/ptaru/akusesutorru/rules/katarogu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
